Skip to content

A connector describes how Playbooks can work with an external service. It identifies the supported operations or provider capability and the authorization needed to use them. A connection is your authorized account binding for that connector.

Choose by the work you need

Begin with the operation, not just the provider name. Reading records, editing content, sending a message, and using a model provider can require different capabilities and permissions.

KindPurposeSetup consideration
IntegrationRead or act on an external systemReview supported operations and account permissions.
MCP serverSupply tools through MCPConfigure and authorize the server separately.
Service providerSupply an eligible managed capabilitySelect the provider in the actual consuming scope.

The available catalog and setup flow show the current supported choices. A provider's broader API does not mean every operation is exposed through its Playbooks connector.

Connect and assign

  1. Find the connector for the service and operation you need.
  2. Authorize the correct external account.
  3. Review the permitted operations.
  4. Assign it to the Agent, Project, or production scope that needs it, where required.
  5. Try a bounded task and inspect the outcome.

Chats use eligible Workspace access under the current person's authority. Agents and Projects require explicit assignments. Development and Site production are separate scopes.

Find a Connector from the Composer

Type /connector and select the available connect or assign action. The command menu reflects the current surface: connecting a Workspace account and assigning it to an Agent or Project are different steps.

You can also select a Connector through mentions when identifying the integration relevant to your request. A reference helps establish which resource you mean; it does not connect an account or grant permission to invoke its operations.

Example: summarize customer activity

Suppose you want a weekly summary from a customer-service system. First check that its Connector supports the records you need to read. Then authorize the intended account and make it available to the receiving resource.

A first request might be:

Read the customer issues from last week in the connected support service. Group them by problem, include links to the original records, and identify any gaps in the available results.

Keep the first result focused on evidence you can inspect. Once the reads work, add a supported write only when you need it—for example, creating a summary record in a specified destination. Explicitly identify that destination and the content to save.

The example depends on the Connector's actual operations. A service with a broad API may expose only a subset through Playbooks.

Understand the setup states

StateMeaningCheck
Listed in the catalogA Connector definition existsSupported operations and consumer scope
Account connectedAuthorization was established for an accountAssignment and current provider permissions
Assigned to a resourceThe resource has an authorized relationshipWhether the requested operation is supported and allowed
Operation completedThat particular operation returned a resultThe result's correctness and any external effect

A Connector does not create a continuously synchronized copy of a service. Ask for the relevant period, filters, and coverage when reading records. If your application needs ongoing ingestion, design that workflow explicitly with its data storage and Jobs.

Provider choices affect operation and billing

Selecting a customer-funded provider can change who pays for upstream consumption. It does not remove Playbooks orchestration, policy, or other platform costs. Connecting an account alone does not replace a managed provider, and provider failure must not be interpreted as permission to use another paid account.

See Connections for account management and MCP servers for adding an external tool provider.