Connectors / Slack

What Deixic does with Slack.

Read and act

Read a thread and reply in the same conversation.

How Deixic helps with Slack.

Read information
Review channels, files and users from Slack as evidence and to check state.
Choose the actions
Deixic supports actions on channels, messages and reactions. Grant only the tools and permissions the task needs.
Keep your decisions
Deixic checks your policy before a change; sensitive changes wait for a named approver. The action record keeps the decision and result.

1 of 25 changing operations require approval. See how approvals work.

Example workflow

Ask the named approver in a thread and keep the answer with the fix

Post the approval request for this pending change in the specified Slack channel. Include what will change, in which system, and the reason. Return the message permalink for the receipt.
  1. Resolve the channel and the approver. Post the request with the system, the exact change, and the policy it falls under, using the post message operation with a plain-text fallback.
  2. Reply in the same thread with the outcome after the change runs and is read back. A thread reply needs the channel and the thread timestamp, so carry both through the task.
  3. Keep the permalink and message identifier with the receipt. The approval itself is recorded by Deixic against the named approver; a Slack message is the notice, not the approval record.

Check before you continue: Losing the thread timestamp posts the reply as a new message in the channel. If the content needs correcting, update the original message instead of posting another. Slack recommends a top-level text fallback for messages with blocks.

Provider reference: Slack message posting and thread replies

Use your existing agent with Deixic. Calls you route through Deixic follow your access and approval policy.

Provider access

Supported Slack reads and actions.

Choose the reads and actions your task needs. Your connection’s permissions and your agent’s access determine what it can use.

Read data

  • Channels Read
  • Files Read
  • Users Read
  • Workspace Read
  • Reactions Read
  • Messages Read
  • Workspace Admin Read

Actions

  • Channels Write
  • Messages Write
  • Reactions Write
  • Files Write
  • Surfaces Write
  • Streaming Write
  • Workspace Admin Write

Permissions

Choose the access for Slack.

Have the account owner authorize the intended account and permissions, and if data is missing, inspect the authorizing user’s access to the target resource before requesting broader access.

To work with Dex in Slack, see Dex in Slack.

Connection
OAuth
Supported operations
Read and act
Reads
7
Actions
7
Provider permissions
Grant only the permissions needed for the task.

What you need to connect

  • Client ID
  • Client secret
  • Access token
  • Refresh token (optional)

Deixic checks calls routed through its gateway and requests approval when your policy requires it.

Reference and troubleshooting

Slack operation reference, troubleshooting, and questionsSOC 2 for Slack

Guides for work in Slack

Why is my Slack bot sending duplicate messages?

Separate Slack event retries, duplicate workers, and repeated sends. Diagnose message duplication without throwing away legitimate events.

Stop letting Slack agents ask questions you already answered

Design Slack agent workflows that read the right thread, resolve conflicting answers, preserve message references, and avoid duplicate replies across tools.

Read the connected-systems series

Connectors for related work

Tell us what you need from Slack.

Bring one task. We’ll show you the access it needs and how Deixic helps.

Request early access

Connector guide by Deixic · Updated