Post notifications and capture conversation context from Slack.
Slack
Post notifications and capture conversation context from Slack.
Flows360 gives operators an end-to-end view of Slack alongside the rest of their stack — sync the objects that matter, run the actions you need, and trigger workflows on real-time events without writing glue code.
—
How to connect Slack (for customers)
You install the Flows360 Slack app into your own Slack workspace. You are not connecting to Flows360's Slack — every workspace gets its own private install with its own bot token, channels, and permissions.
Option A — Connect from Flows360 (recommended)
1. In Flows360, go to Connectors → Slack → Connect.
2. You'll be redirected to Slack and asked to choose the workspace to install into.
3. Review the requested permissions and click Allow.
4. Slack sends you back to Flows360 — the connection is live.
Option B — Install from the Slack App Directory
1. In your Slack desktop or web client, click your workspace name → Tools & settings → Manage apps.
2. In the App Directory search bar, type Flows360 and select our app.
3. Click Add to Slack and approve the permissions.
4. Return to Flows360 and click Connect on the Slack connector — it will detect the existing install and link it to your tenant.
Permissions we request
| Scope | Why we need it |
|—|—|
| `chat:write`, `chat:write.public` | Send messages from flows |
| `channels:read`, `groups:read` | Let you pick channels in the UI |
| `channels:history`, `groups:history` | Read message context for triggers |
| `im:write`, `im:history` | Send and read direct messages |
| `users:read` | Resolve user IDs to names |
You can review and revoke these anytime in Slack → Manage apps → Flows360 → Configuration.
Inviting the bot to private channels
The bot is automatically available in public channels. For a private channel, type `/invite @Flows360` in that channel once.
Troubleshooting
- "not_in_channel" error — invite the bot to the channel (see above).
- "missing_scope" error — disconnect and reconnect from Flows360; we'll request the updated scopes.
- Workspace admin restricts app installs — your Slack admin needs to approve the Flows360 app first under Manage apps → App Management Settings.
Common use cases
- Route any Flows360 workflow alert to a Slack channel
- Trigger workflows when a Slack message matches a pattern
- Run approval flows via Slack message buttons
Sync scenarios
- Post CRM deal updates into a Slack channel
- Open a Slack thread when a P1 ticket arrives
- Mirror Slack channel decisions back to the CRM as activities
Objects supported
- Message
- Channel
- User
- User Group
- Reaction
- File
- Thread
- Workspace
Actions
- send_message
- list_channels
- message_received
- invite_to_channel
- set_channel_topic
- update_status
- archive_channel
- add_reaction
- user_joined_team
- reaction_added
- channel_created
Frequently asked questions
Does this work with Slack Connect channels?
Yes — shared channels are supported as a first-class destination.
- Auth method: OAuth 2.0
- Required scopes: 9
- Supported objects: 8
- Supported actions: 7
Overview
The Slack connector allows for programmatic interaction with a Slack workspace. It enables sending and receiving messages, managing channels, and monitoring user activity. By connecting Slack, operators can automate notifications from other systems, create workflows triggered by Slack events like new messages or reactions, and sync conversation data for a unified operational view. This eliminates the need for manual context switching and glue code, enabling seamless integration of real-time communication into automated processes.
All API calls are authenticated via an OAuth 2.0 token generated on a per-workspace basis. Each connected workspace has a unique bot user and token, ensuring data isolation.
Setup steps
Follow these steps to install and configure the Slack connector.
Option A: Connect from Flows360 (Recommended)
1. In the Flows360 UI, navigate to Connectors
2. Select Slack and click Connect.
3. You will be redirected to Slack's OAuth 2.0 authorization screen.
4. Choose the target Slack workspace to install the app into.
5. Review the requested permissions and click Allow.
6. Slack will redirect you back to Flows360. The connection is now active and ready to use.
Option B: Install from the Slack App Directory
1. In your Slack desktop or web client, click your workspace name, then navigate to Tools & settings > Manage apps.
2. In the App Directory search bar, enter `Flows360` and select the application.
3. Click Add to Slack and approve the required permissions for the installation.
4. Return to the Flows360 UI and navigate to Connectors > Slack.
5. Click Connect. Flows360 will detect the existing installation and link it to your tenant.
Required scopes
chat:writechat:write.publicchannels:readgroups:readchannels:historyreactions:writechannels:manageusers:readteam:read
Supported objects
- Message
- Channel
- User
- User Group
- Reaction
- File
- Thread
- Workspace
Supported actions
- Send Message — Sends a message to a specified channel, user, or thread. Supports attachments and block kit formatting.
- List Channels — Retrieves a paginated list of all public channels in the workspace.
- Invite to Channel — Invites a specified user to a channel. The bot must be a member of the channel.
- Set Channel Topic — Sets the topic for a specified channel.
- Update Status — Updates the installing user's status emoji and text.
- Archive Channel — Archives a specified channel. The channel must not be the default #general channel.
- Add Reaction — Adds a reaction (emoji) to a specific message, identified by its timestamp and channel ID.
Use cases
- Customer 360
- Marketing Automation
- Revenue Operations
- Support Ticket Sync
- HR & People Ops
Limitations
- All actions are subject to the rate limits of the Slack API. Refer to the [Slack API Rate Limits documentation](https://api.slack.com/docs/rate-limits) for details.
- Messages sent via `chat.postMessage` have a maximum length of 40,000 characters.
- The bot user must be a member of a private channel to read messages from or post messages to it.
- File uploads are limited to 1 GB per file.
- The `list_channels` action returns a maximum of 1,000 channels per call and may require pagination for workspaces with more channels.