You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/slack.mdx
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,18 @@ With the Slack integration in Sim, you can:
28
28
29
29
In Sim, the Slack integration enables your agents to programmatically interact with Slack as part of their workflows. This allows for automation scenarios such as sending notifications with dynamic updates, managing conversational flows with editable status messages, acknowledging important messages with reactions, and maintaining clean channels by removing outdated bot messages. The integration can also be used in trigger mode to start a workflow when a message is sent to a channel.
30
30
31
+
## Stream Trigger Responses
32
+
33
+
Custom-bot Slack triggers can stream workflow outputs directly back into the conversation that started a run. Enable **Stream response to Slack** on a Message, App Mention, or Assistant Thread Started trigger, then select the outputs to deliver.
34
+
35
+
- A selected Agent output streams as it is generated. Intermediate pre-tool turns are held back so only the final answer is appended.
36
+
- A selected non-streaming block output is sent when that block invocation completes.
37
+
- Loop and parallel invocations each create their own Slack response.
38
+
- Optional thinking and tool-call updates appear as Slack tasks in a timeline or plan.
39
+
- Slack Agent Sessions remain in processing state for the run, return to active when it finishes, and the native Slack stop button cancels active workflow executions.
40
+
41
+
Automatic trigger responses require a custom bot created by the Slack setup wizard. They are not available with the shared Sim Slack app.
42
+
31
43
## AI-Generated Content
32
44
33
45
Sim workflows may use AI models to generate messages and responses sent to Slack. AI-generated content may be inaccurate or contain errors. Always review automated outputs, especially for critical communications.
|`eventType`| string | Yes | The single Slack event this trigger fires on. Add another trigger block for another event. |
1993
2005
|`customBotCredential`| string | Yes | Choose a custom Slack bot you set up once and reuse across triggers. |
1994
2006
|`manualBotCredential`| string | Yes | Set the custom bot credential ID directly. |
2007
+
|`streamResponse`| boolean | No | Stream selected workflow outputs into the Slack conversation that started this run. Custom bots only. |
2008
+
|`streamOutputs`| workflow-output-selector | No | Each selected block invocation creates its own Slack response. Agent outputs stream live; other outputs are sent when the block completes. |
2009
+
|`streamIncludeThinking`| boolean | No | Show agent thinking as Slack task updates while the response is generated. |
2010
+
|`streamIncludeToolCalls`| boolean | No | Show tool execution lifecycle as Slack task updates. |
2011
+
|`streamTaskDisplayMode`| string | No | Choose how Slack displays thinking and tool progress. |
1995
2012
|`source`| string | No | Restrict to direct messages, public channels, or private channels. Leave empty to match any. |
1996
2013
|`channelFilter`| channel-selector | No | Restrict to specific channels. Leave empty to trigger on any channel the bot has been added to. |
1997
2014
|`manualChannelFilter`| string | No | Comma-separated channel IDs to restrict to. Set IDs directly here. |
Copy file name to clipboardExpand all lines: apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/editor/components/sub-block/components/index.ts
Copy file name to clipboardExpand all lines: apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/editor/components/sub-block/sub-block.tsx
0 commit comments