Docs · Platform
How Connections works
Configure once, govern each use.
1Connect the tool
A connector authenticates a specific provider account or workspace, and that configured relationship is a connection.
2See what Dex can read and change
The connector lists supported operations; provider permissions and each agent's access decide which it can use.
3Put writes behind policy
Writes and deletes follow your approval rules, deletes are marked destructive, and each leaves a signed receipt.
4Use it from any surface
A connection stays available in Slack, the app, or Deixic Code without changing the agent's authority.
How actions are labeled and checked
- Every action has a declared effect
- The catalog labels each action read, write, or delete, and flags approval and destructive actions.
- Strict inputs
- Actions accept only the fields their schema allows, so a model cannot add extra parameters.
- Checked after it runs
- For connectors that expose a read of the changed record, Deixic confirms the change with a separate read instead of trusting the provider response alone.
- Uncertain writes get reconciled
- Inspect the recorded outcome and reconcile the destination before retrying; recovery depends on the provider's idempotency support.
- Credentials you control
- Monitor connection health, and rotate or revoke managed credentials from Deixic.
- Your own MCP servers
- Deixic Code connects to your MCP servers over stdio or HTTP, with OAuth sign-in and OS-keychain tokens.