Connect Slack to your agent fleet.
Put supported Slack actions under policy and keep their decisions with the result.
What Deixic uses from Slack
- Channels Read
- Channels Write
- Files Read
- Users Read
- Workspace Read
- Messages Write
- Reactions Read
- Reactions Write
- Files Write
- Surfaces Write
- Streaming Write
Provider access
See what Slack can read or change.
Read data
- Channels Read
- Files Read
- Users Read
- Workspace Read
- Reactions Read
Actions
- Channels Write
- Messages Write
- Reactions Write
- Files Write
- Surfaces Write
- Streaming Write
Permissions
Connect Slack with customer-approved provider access.
- Connection
- Customer authorized
- Access
- Read and act
- Reads
- 5
- Actions
- 6
- Provider permissions
- Grant only the permissions needed for the reads and actions shown above.
Approval example
Put Channels Write behind policy.
- 01The agent requests the connected Slack action.
- 02Deixic checks agent identity, target, recorded cost, and policy.
- 03A sensitive action waits for the named business or system owner.
- 04The decision and connector result remain in activity history.