Setting up a connector

1 · Org admin or developer adopts the connector

Org Settings → Integrations → find the connector → Enable. Some connectors support multiple named instances (e.g. two separate Salesforce accounts) — give each instance a name when you adopt it; everywhere else in the platform refers to it by that name. This step makes the connector selectable for automations and logic blocks across the org, and stages it (disabled) for every workspace.

2 · Org admin or developer maps its actions (Customize)

Open the connector's Customize panel. For a connector whose actions take business data (Salesforce, Slack, and similar), an Actions tab lets you configure each action:

• Source entity — which entity this action's data is about, if any.
• Source lookup field — which field identifies the specific record (defaults to the record's own id).
• Related entities — other entities this action's field mapping can also pull from.
• Field mapping — for every field the action declares, a value: a literal, a field on the source entity, a field on a related entity, or left for the caller to supply.

A connector with inbound events (a payment connector's webhook) has a separate Webhook tab instead — see Payment connectors.

3 · Tenant admin enters credentials

Tenant Settings → Connectors → select the connector → Credentials → enter the fields the connector's auth type calls for (an API key, a bot token, a webhook URL, etc.) → Save. This section saves independently of everything else on the screen — saving credentials never touches field mapping or vice versa. Secret fields are encrypted; nothing entered here is ever returned by any API.

A few credential-adjacent fields aren't secrets at all — a webhook connector's target URL, for instance, is stored the same way but isn't encrypted, since it isn't sensitive.

Field sources, in one place

Every field on a connector action is tagged with where its value comes from — this determines who can (or must) supply it, and where you'll see it:

• caller (the default) — whoever invokes the action supplies it: your app's request, the automation author's field mapping, or the logic block author's field mapping.
• tenant — filled automatically from the tenant's own saved settings (e.g. a checkout's success/cancel URLs). Never something a caller supplies.
• org — set once by the org admin or developer, applies to every workspace.
• identity — stamped automatically from whoever is authenticated when the call is made (their user id, email, or name) — never accepted from the request, so it can't be spoofed to attribute an action to someone else.