How connectors work
What a connector can read and write, and what it is never given.
On this page
A connector is a scoped link to another system. It is deliberately narrow.
Read and write are separate
Every connector is configured with its own read scope and write scope, and they are set independently. A connector that reads payment status and writes nothing is a normal, common configuration.
Default to read-only and add write scopes when a workflow actually needs one. It is much easier to widen a scope than to explain a write nobody expected.
What a connector is never given
- Access to cases outside the teams it is configured for
- Your Notion, email or identity credentials — each integration authenticates separately
- The ability to grant itself scopes; scope changes are an Administrator action and appear in the audit log
What gets recorded
Every connector read that informs a worker action appears in that action's Sources panel. Every connector write appears on the case timeline as its own entry naming the connector.
This is what makes an integrated case explainable. "The system updated it" is not an answer; "the Finance connector wrote payment status at 14:02, triggered by workflow step 3" is.
Rate and failure
Connectors retry a failed call three times with backoff, then record the failure on the case timeline and continue. They do not block a case.
Adding one
Settings → Integrations, choose the system, authenticate, then set scopes. Test against a single case before enabling it for a case type.