Skip to content

Connectors and approvals

A playbook declares which outside operations it needs. The workspace resolves each requirement to an authorized connection. An approval governs a particular action within a run. These are three separate decisions.

Layer Lane example
Requirement The research playbook needs an Exa search. The outreach playbook needs Gmail send.
Connection The workspace uses the appropriate authorized account to satisfy that requirement. A personal requirement resolves to the acting person’s account. A shared app destination is set up separately.
Approval A person reviews the actual recipient and message before the configured send step runs.

A connector step can read, write, or start a process whose result arrives later. A read can contribute evidence to a goal. A write can have an external effect, such as sending an email. When a required operation lacks a valid connection, the runtime holds the affected work.

A connector declares operations. A connection binds those operations to an account, using credentials stored in the vault. Playbook packages and persona definitions carry requirements and references; they do not carry the account’s secrets. Each workspace supplies its own authorized connections.

Agents executing playbooks and custom apps can use the same declared connector operations, subject to their own grants. Data flows through those operations; credentials remain behind the connection boundary. An externally hosted custom interface uses its authorized app bridge rather than receiving provider credentials.

The team needs a domain specialist to resolve cases its playbooks cannot decide. If two CRM records share a domain, the agent presents both candidates, their source evidence, and the decision the run is waiting for. The specialist can confirm the correct record, supply a correction, or reject the proposed match. Work that depends on the match waits for that decision.

Resolving the anomaly establishes which record to use. If the next step sends an email or changes a protected CRM field, its approval covers the exact proposed effect and uses the workspace’s normal permissions. Keep the decision and evidence with the run so the expert can review patterns and improve the rules. See the improvement loop.

Before a protected effect, the playbook can rehearse the proposed change with a test connector or another isolated environment. Review the rehearsal evidence with the exact live proposal. See governed execution for when to repeat the rehearsal and what the runtime checks before dispatch.

Connectors helps the team see which operations it needs and resolve missing setup. Vault handles account credentials and sensitive settings. Approvals presents the decisions that a run is waiting for. An approved action is tied to the reviewed details of that action. Editing the draft or changing the connector assignment can require another decision. Shared publication also requires an owner-approved destination and the member’s consent for the fields being shared.

See the connector requirement fields, step types and effects, and runtime capability report. The implementation guide walks through the binding and publishing steps. The skill catalogue covers persona integrations and team setup.

Meeting desk reads upcoming events under the acting member’s calendar grant. Its publisher points to an authorized destination. Review the operations and account contexts independently, including whether the destination is a team list or an external channel.

Calendar read → authorized source account → candidate meeting brief
Review brief → proposed destination, acting account, and exact content
Publish brief → recheck grant and approved scope → record outcome

If the operator changes the channel after approval, show the proposed publication again with its new destination. If the provider outcome is uncertain, reconcile it before retrying. This preserves the connection between the human decision and the provider action.

See connector requirements, Vault, and approvals.