Documentation

Connect your marketing data to Claude, ChatGPT and other LLMs.

Connect n8n & Make

Both n8n and Make talk to gadspilot over plain HTTP using a Personal Access Token (PAT) — the same token used for any headless agent. Generate one from your Meta Ads dashboard (see Headless agents for the full walkthrough).

n8n — HTTP Request node

  • Method: POST
  • URL: https://gadspilot.com/mcp-meta
  • Authentication: Generic → Header Auth → Name Authorization, Value Bearer YOUR_TOKEN
  • Body: JSON (raw), Content-Type application/json

List the available tools:

{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }

Then call a tool (example — adjust the tool name/arguments to your scope):

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": { "name": "list_accounts", "arguments": {} }
}
💡
If your n8n version ships the native MCP Client node, point it at https://gadspilot.com/mcp-meta with transport HTTP and add the Authorization: Bearer YOUR_TOKEN header — it will auto-discover the tools.

Make (Integromat) — HTTP module

  • Module: HTTP → “Make a request”
  • URL: https://gadspilot.com/mcp-meta · Method: POST
  • Headers: Authorization: Bearer YOUR_TOKEN and Content-Type: application/json
  • Body type: Raw → JSON, with the JSON-RPC payload above
  • Parse the response with a JSON module to map tool results into your scenario.
The PAT is a full credential. In n8n store it as a Credential, in Make as a Connection/data store — never paste it directly into a shared scenario. Revoke it from your dashboard if it leaks.
Besoin d'aide ? Demandez à Léa 💬
gadspilot assistant
Léa
Assistante IA · gadspilot
Besoin d'un humain ? Contacter le support