Connecting your tools
Let your agent act in the apps you already use — Slack, Gmail, Salesforce, Notion, and more — with per-action controls.
Connectors let an agent take actions in external tools and services on your behalf — send a Slack message, file a ticket, query a database. You choose which tools a project can reach and exactly what each one is allowed to do.
Connectors are managed per project under Customize → Connectors.
Add a connector
Choose how to connect
Open Customize → Connectors → Add, and pick the kind of tool:
- An app from the catalog — hundreds of popular apps (Slack, Gmail, Salesforce, Notion, GitHub, and more) connect with a guided, one-click flow.
- A custom service — bring your own via an MCP server, an OpenAPI or GraphQL spec, or a plain HTTP base URL, when the app isn't in the catalog.
Connect credentials
- Catalog apps use a one-click connect — you authorize the app and the connection completes; no keys to copy.
- Custom services authenticate with a credential you provide (a bearer token, basic auth, or a custom header). Store the value as a project secret and reference it by name — it never lands in your repo.
Choose whether a connector's credentials are shared across the project or per-user, so each member acts as themselves where that matters.
Set what it's allowed to do
For each connector you control its actions. Set a rule per tool — or a pattern matching many — to one of:
- Allow — the agent runs it without asking.
- Ask — the agent pauses for your approval before running it.
- Block — the agent can never run it.
Set a global default (for example, ask before anything that writes), then carve out specific allows and blocks. This is how you let an agent read freely while still approving anything that sends, deletes, or charges.
Share a connector
Decide who on the project can use a connector: the whole project, specific members, or keep it private to you. Pair this with per-user credentials when each person should act under their own account.
Stay in control
- Nothing is connected unless you connect it.
- Every action is governed by your Allow / Ask / Block rules.
- Disconnect a tool any time it's no longer needed.
Connectors are configured as code in your manifest, so a project's tool access is reviewable and versioned — you can always see what it can reach and why.
Related: Managing secrets · Connections concept · Customizing your project.