Use integrations in Playbooks

Playbooks use MCP integrations to read external data and take approved actions. Add an integration only when a step needs it.

Define the need

For each integration, state what the Playbook needs from it. For example, a step may read a CRM record, retrieve a file, or create a task after human approval.

Declare every integration that the Playbook requires. V7 Go can then identify a missing connection before the run starts.

Keep external actions safe

Use explicit instructions for any external action. State when the Playbook must ask for approval, what it may change, and what evidence it must return.

Technical notes

The required integration list controls connection readiness. Step-level integration labels help people see which app a step uses, but they do not limit the tools that the step can use at run time.

An interactive run can pause while a user connects a required service. A scheduled or API-started run can fail when a required connection is missing. Do not replace a missing connection with invented data.