Slack
The Slack node is an enterprise-grade communication module that allows your automated workflows to seamlessly interact with your Slack workspaces. Dispatch critical system alerts, manage community channels, upload robust analytical reports, and coordinate team notifications instantly with zero-latency.
What can you do with Slack?
Robust Message Dispatch
Send beautifully formatted markdown messages, @mention specific users, and dynamically update or delete existing messages to keep your channels perfectly clean and informative.
V2 File Upload & Management
Leverage Slack's modern V2 File API to upload massive log files, PDF invoices, or CSV reports directly into channels without hitting legacy memory limits.
Smart Resiliency & Rate Limiting
Built for production. Features aggressive OOM (Out of Memory) protection, Connection Pooling, and native Exponential Backoff to gracefully handle Slack 429 Rate Limits and 5xx Server Drops.
Detailed Usage & Configuration
The Slack node is designed for high-throughput production environments. It natively handles authentication via OAuth2 and boasts powerful resiliency features like polymorphic responses and smart retries.
1. Common Operations
- Send/Update Message: Dispatch critical Error Trigger payloads directly to your DevOps channel. You can even choose to post as a custom Bot or "As User".
- File Uploads: Seamlessly upload physical files (like a generated PDF invoice) or raw string text directly to a specific channel. The node automatically handles the complex 3-step V2 Upload process securely.
- Channel Management: Automatically create private project channels, invite a list of user IDs, or archive channels when a project workflow completes.
2. Polymorphic Responses
For advanced workflow routing, toggle the Return Full Response property.
- Disabled (Default): Returns the raw JSON payload natively (e.g.
{ "ok": true, "message": {...} }). - Enabled: Wraps the data and exposes the raw HTTP context:
{ "data": {...}, "statusCode": 200, "headers": {...} }. This allows you to inspect Rate Limit headers or route flows based on specific HTTP status codes.