--- title: "Slack Integration" description: "Give AI agents a voice in your workspace. Slack triggers activate workflows on messages, mentions, and reactions. Agents send updates, route exceptions, and collect human decisions without leaving Slack." url: https://flowrunner.ai/integrations/slack date_modified: 2026-08-01T02:40:32-07:00 --- # Slack [Communication](https://flowrunner.ai/integrations/category/communication-messaging) Give AI agents a voice in your workspace. Slack triggers activate workflows on messages, mentions, and reactions. Agents send updates, route exceptions, and collect human decisions without leaving Slack. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 8 triggers · 16 actions · OAuth · available [Slack website](https://slack.com/) · Capability data verified 2026-08-11 1. AP agent processes purchase orders overnight and detects 3 exceptions 2. Agent posts batch summary to finance-ops channel with total count and exception count 3. Agent sends individual Slack messages for each exception with Approve and Escalate buttons 4. Finance manager approves two exceptions from phone via interactive buttons 5. Agent resumes posting approved POs to ERP automatically 6. Escalated exception routed to finance director with full context 7. Each exception decision captured with approver identity in audit trail ## What This Integration Enables Slack is not just a notification tool for FlowRunner agents. It is the primary interface for human-in-loop orchestration. Agents use Slack to surface exceptions, request approvals, deliver structured reports, and collect decisions that resume downstream automation. When an agent pauses because it hit something it should not decide alone, the question lands in Slack with full context. ### Without FlowRunner **Exception emails**: AP exceptions sent via email and tracked in separate threads **No structured approval**: Exceptions require a meeting or email chain before resolution **Manual status tracking**: Managers ask team members directly to get a status on open items ### With FlowRunner **44-of-47 processed overnight**: Routine POs post without anyone touching them **6-minute exception resolution**: Three exceptions approved and escalated in one Slack session from a phone **Decision audit trail**: Every approval captured with approver identity and timestamp automatically ## Use Case Scenarios ### Exception Routing with Interactive Approval An AP agent processes purchase orders overnight. At 7am, it posts a summary to #finance-ops: "44 of 47 POs matched and posted. 3 require review." Each exception appears as a Slack message with the discrepancy highlighted and two buttons: Approve and Escalate. A finance manager approves two from their phone. The third gets escalated. The agent resumes posting the approved POs to the ERP. Total time from exception to resolution: 6 minutes. ### Inbound Document Processing Your ops team has a #vendor-docs channel. When a vendor drops a PDF invoice into the channel, On File Shared fires. The agent downloads the file, runs it through the document parser, validates fields against the PO database, and posts a structured summary back in the thread. If everything matches, it posts to the ERP automatically. If not, it surfaces the specific discrepancy with context for the ops team to resolve. ### Scheduled Status Digests Every Monday at 8am, an agent compiles the week's workflow metrics: executions run, exceptions escalated, decisions made, time saved. It posts a formatted report to #operations using Block Kit for clean visual structure. Leadership gets operational visibility without pulling reports manually. ## Human-in-Loop Highlight Slack is where FlowRunner's "Agents That Ask" capability lives day to day. When an agent encounters a decision that should not be automated, it does not fail or skip. It sends a Slack message with the full context of what it found, what options are available, and what it needs from the human. Interactive buttons powered by the On Block Action trigger collect the decision and route it back to the workflow. The agent resumes with the human's input preserved in the audit trail. Your team handles exceptions. The agent handles everything else. Agent processes routinely Detects decision that should not be automated Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 16 actions ### Messaging 7 - **Send Message to Channel** The agent posts updates, alerts, or structured reports to any channel. Used when a workflow completes, an exception surfaces, or a status update needs broadcasting. Example: after processing 47 invoices overnight, the agent posts a summary to #ap-team at 8am. - **Send Direct Message** Routes a message to a specific user rather than a channel. Used for personalized exception routing: the agent contacts the right person with the right context without interrupting the whole team. - **Update Message in Channel** Edits a previously sent message. Used to reflect status changes in real time: an agent posts "pending review" then updates to "approved" when the decision comes back. - **Delete Message in Channel** Removes a message. Used for cleanup after time-sensitive alerts are resolved. - **Get Latest Channel Messages** Reads recent messages from a channel. Used when agents need to understand current conversation context before acting. - **Get Latest Thread Messages** Retrieves thread replies on a specific message. Used to collect all decision-maker responses before resuming a workflow. - **Get Message** Fetches a specific message by timestamp. Used for targeted retrieval in audit or reconciliation workflows. ### Channels 6 - **Create Public Channel** Creates a new public channel. Used when agents spin up project-specific workspaces automatically, for example, a new M&A due diligence channel when a deal enters the pipeline. - **Create Private Channel** Creates a private channel. Used for sensitive workflows where only specific stakeholders should see agent communications. - **Find Channel** Locates an existing channel by name. Used before sending to verify the target exists. - **Invite User to Channel** Adds a user to a channel. Used when agents provision access as part of onboarding or project creation workflows. - **Kick User from Channel** Removes a user from a channel. Used for offboarding or access management automation. - **Search Messages** Queries message history across the workspace. Used to retrieve prior decisions or context for current workflow steps. ### Members 2 - **Find Member** Looks up a single workspace member. Used to resolve a name or email into a Slack user ID before routing a message. - **Find Members** Returns a list of members matching search criteria. Used when an agent needs to identify team members for notification or routing. ### Files 1 - **Get File Info** Retrieves metadata about a shared file. Used when an agent needs to process a document that a team member posted in Slack. ## Triggers 8 triggers ### Event Triggers 8 - **On Mention** Fires when a user or bot is mentioned in a message. Start workflows from a simple @flowrunner mention. Example: @flowrunner run invoice validation triggers the AP agent to begin its process immediately. - **On Channel Message** Fires when any message is posted to a monitored channel. Used to kick off processing workflows when inbound data arrives via Slack: a team member pastes a vendor email and the agent begins parsing it. - **On Block Action** Fires when a user clicks an interactive button or element in a Block Kit message. This is the primary mechanism for human-in-loop decisions: the agent sends a message with Approve/Reject buttons, and the decision fires this trigger to resume the workflow. - **On Reaction Added** Fires when someone adds an emoji reaction to a message. Used for lightweight approval workflows: a thumbs-up reaction on a message resumes the agent's next step. - **On New Member** Fires when a user joins a channel. Used to trigger onboarding workflows when someone is added to a project or team channel. - **On Channel Created** Fires when a new channel is created. Used to trigger setup or provisioning workflows automatically when new project spaces appear. - **On File Shared** Fires when a file is uploaded to a channel. Used to trigger document processing workflows automatically when a team member drops a file in a designated channel. - **On Message from Query** Polls for messages matching specific criteria at configurable intervals. Used for monitoring use cases where real-time webhooks are not available. ## Frequently Asked Questions ### What can FlowRunner do with Slack? FlowRunner agents can run Find Member, Find Members, and Find Channel in Slack, plus 13 more actions. ### Does connecting Slack to FlowRunner require OAuth? Yes. Slack connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Slack trigger a FlowRunner workflow automatically? Yes. Slack supports 8 triggers that can start a FlowRunner workflow automatically. **Work at Slack?** This integration exposes Slack to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/slack. Site index: https://flowrunner.ai/llms.txt