Integrations
Slack
Send channel messages or direct messages, create a public channel, and invite a user to a channel.
What this guide covers
- A Slack workspace through OAuth with access to the intended channels and users.
- 4 supported workflow actions.
- Slack workspace administrators can limit app installation and channel access. Use the least-privileged workspace and channels for the workflow.
- Channel IDs and user IDs are not display names.
What Slack connects
A Slack workspace through OAuth with access to the intended channels and users.
Send channel messages or direct messages, create a public channel, and invite a user to a channel.
Prerequisites and permissions
- Permission to install or authorize the Yanola Slack connection
- Exact channel ID or user ID required by the action
- Workspace policy that permits the requested operation
Slack workspace administrators can limit app installation and channel access. Use the least-privileged workspace and channels for the workflow.
Connect and configure
- Open the intended Agent Project → Integrations.
- Find Slack and select Connect.
- Complete authorization with the correct external identity.
- Confirm the returned connection status is active.
- In the workflow builder, add App Action.
- Select Slack, choose one supported action, select the connection, and complete the fields Yanola displays.
- Save and test with controlled data before activation.
Supported actions
| Action ID | What it does |
|---|---|
send_channel_message | Send a message to a Slack channel by channel ID. |
send_direct_message | Open a DM and send a message to a Slack user. |
create_channel | Create a public Slack channel. |
invite_user_to_channel | Invite one Slack user to a channel. |
Example workflow
Post a high-priority message to a support channel when a Human Handoff is created.
Workflow Trigger → Validate inputs → App Action (Slack) → Condition → Notify or End FlowReconnection and token expiration
- Open Integrations when a workflow reports a missing, expired, revoked, or error connection.
- Select Reconnect for Slack.
- Authorize the intended identity again.
- Validate access to the exact resource used by the workflow.
- Retest every dependent App Action.
Troubleshooting
| Symptom | What to check |
|---|---|
Connection is expired, revoked, or error | Reconnect from Integrations and complete provider consent. |
Action cannot find a resource | Grant the connected identity access and use the exact provider ID. |
Action input is rejected | Match the action-specific fields and data types shown in the node. |
Test and live behavior differ | Check provider environment, current permissions, external rate limits, and live data. |
Limitations and security
Channel IDs and user IDs are not display names.
The catalog creates public channels only; it is not a general Slack administration interface.
Never place provider access tokens or secrets in workflow text, logs, screenshots, or AI prompts. Remove unused connections and reconnect only through Yanola.