Integration platforms

Short reference for Zapier, n8n, and Make as MCP backends. Always follow the vendor’s current MCP and auth documentation; URLs and auth schemes change.

API key on the downstream connector

Each integration platform’s MCP HTTP endpoint expects an API key (or equivalent token) issued by that vendor. In Agentsyx Creator, set it on the downstream connector that points at that MCP URL—the same connector configuration you use for any downstream MCP server. Agentsyx forwards the credential when it calls the platform (commonly as Authorization: Bearer …; exact scheme is defined by the vendor). Overview of outbound headers: Inputs to downstream servers.

Zapier

• Use Zapier MCP so the model sees tools backed by your connected integrations (apps and actions you enable in Zapier).
• Store secrets in Zapier; pass only minimal arguments from the model.
• Prefer a small, focused set of integration actions per concern so failures and retries are easy to trace; avoid overly broad tool surfaces.
• Agentsyx always injects platform context (headers and, for MCP downstream, a small mirrored set of tool arguments), and you can optionally tag parameters in Creator—see Injected parameters & metadata for why and what differs.

n8n

• Use n8n’s MCP support (or community patterns) to expose workflows.
• Keep workflow inputs small and typed; validate in the workflow before side effects.

Make

• Use Make MCP to expose scenarios as tools.
• Watch operations quotas; map expensive tools to higher credit prices upstream.

Agentsyx Creator

Register each integration as its own downstream connector (MCP URL plus API key as above), then map selected tools on the upstream connector. See Understanding Connectors.