Loading…
How do playbooks connect to external systems?
TL;DR: Playbooks reach the outside world three ways: connect an external MCP server and call its tools, make direct HTTP calls (or define reusable custom HTTP tools), and use SDKs inside Code steps. Credentials are always supplied from Secrets — never hardcoded — and referenced with ${VAR} in headers and steps.
Who this is for
Developers wiring playbooks to APIs, SaaS tools, databases, and SDKs.
What are my options?
| Approach | Use it for | Doc |
|---|---|---|
| MCP connectors | Services with an MCP server (Slack, Linear, GitHub, Stripe, …) | Connect external MCP servers |
| HTTP and custom tools | Any REST/HTTP API, including ones you wrap as reusable tools | HTTP and custom tools |
| SDKs in Code steps | Calling an SDK (including AI SDKs) from code | HTTP and custom tools |
All of these read credentials from Secrets.
How do I choose?
- If the service publishes an MCP server, connect it — you get typed tools with OAuth or API-key auth and no glue code.
- If it's a plain REST API, use an HTTP step, and promote it to a custom tool when several playbooks need it.
- If you need data transforms, batching, or an SDK, do it in a Code step.