1. Open Add Platform Integration
- In the Integrations section, go to Platform Integrations.
- Click Add Credential.
- From the list of available integrations, select Slack.
- You’ll be redirected to the Slack Integration Setup page.
2. Slack Authorization

- A notification box appears showing the organization ID (e.g.,
org_lAowz6o1YKbB4YUt) that will be used for this integration. - The integration status shows as Ready for authorization.
- Click Authorize with Slack to begin the OAuth flow.
- You’ll be redirected to Slack’s permissions page.
- Select the Slack workspace where you want to install Kubiya.
- Review the requested permissions:
- Send messages as Kubiya
- View basic channel information
- Post updates and respond to commands
- Access public channels and DMs where Kubiya is invited
- Click Allow to approve and complete authorization.
3. Connect and Finalize Integration
Once authorization is complete:- Kubiya validates your Slack workspace and generates a secure token for communication.
- The connection status changes to Active, and the integration appears in your Platform Integrations list.
- You can now use the Slack integration for:
- Triggering workflows via Slack messages or slash commands.
- Receiving task status updates, notifications, and completion summaries directly in Slack channels.
- Collaborating with agents by issuing instructions from within Slack.
4. Managing the Slack Integration
You can manage all connected Slack workspaces from Integrations > Platform Integrations > Slack. Available Actions- View Details: Displays the connected organization ID, workspace name, and authorization status.
- Reauthorize: Reconnect Slack if authorization expires or permissions change.
- Remove Integration: Disconnect the Slack workspace safely when no longer in use.
- Add Additional Workspace: Use Add Credential again to connect multiple Slack workspaces to the same organization.
5. Permissions Requested
Kubiya’s Slack integration uses OAuth 2.0 and requests only the permissions necessary for workflow automation and communication. Common Permissions:chat:write– Send messages as Kubiya.channels:read– Access metadata for public channels.groups:read– Access metadata for private channels where Kubiya is invited.im:readandmpim:read– Read messages from direct or multi-party conversations involving Kubiya.commands– Allow users to invoke Kubiya commands via/slashshortcuts.
6. Troubleshooting
| Issue | Possible Cause | Resolution |
|---|---|---|
| Authorization popup does not open | Browser blocking pop-ups | Allow pop-ups or retry in incognito mode |
| Slack workspace not listed | User lacks permission to install apps | Contact your Slack workspace admin to authorize the Kubiya app |
| Integration shows inactive | OAuth token expired | Click “Reauthorize” in the integration settings |
| Messages not posting | Kubiya not invited to the channel | Add Kubiya to the target channel using /invite @Kubiya |
7. Security Notes
- All Slack OAuth tokens are encrypted and stored securely in Kubiya’s credential system.
- Only authorized workspace admins can add or remove Slack integrations.
- Kubiya operates with the minimum permissions required for workflow automation.
- Revoking permissions from Slack will automatically disable associated workflows in Kubiya until reauthorization.