ChatPilot
Connected systems

Zapier, Make, n8n and webhooks

For tools without an MCP server: define actions yourself and let ChatPilot post them as JSON to a webhook when you press Run.

A webhook is an address that takes a message and starts something in another tool. Through Zapier, Make or n8n that reaches thousands of apps, and your own software can take one too. ChatPilot never reads from a webhook; it only sends the actions you define, when you press Run.

Add one

  1. Settings → Connected systems → ＋ Add system, then under Or a webhook pick Zapier, Make, n8n or Webhook.
  2. Get the address in the other tool (see Where to find the address below).
  3. Fill in Name and Webhook URL. Optionally a Secret header (e.g. X-Webhook-Secret, or Authorization with Bearer … as the secret) and its Secret.
  4. Define one or more actions with ＋ Action (see An action below).
  5. Click Connect. Actions that create something are on; the others wait until you switch them on.

Where to find the address

  • Zapier: a Zap whose trigger is Webhooks by Zapier → Catch Hook; copy its webhook URL.
  • Make: a scenario that starts with Webhooks → Custom webhook; copy its address.
  • n8n: a workflow that starts with a Webhook node (method POST); use its production URL. http:// works for an n8n on your own network.
  • Webhook: any address that takes a JSON POST.

An action

  • Action: its name, e.g. "Create lead" or "Add task".
  • What happens: one sentence.
  • Risk: creates something, changes something, sends a message, deletes something or involves money. A name like "Refund" or "Delete" counts as that risk whatever you pick.
  • Fields (＋ Field): the name in the JSON, the label on the card, where its value comes from (you type it, from the chat, from the contact or always the same), its type, and whether it's required.

The address and the secret go into your computer's secret store: whoever has a webhook address can post to it.

Send a test

Send a test next to an action posts its fields with placeholders only, no chat data, so Zapier, Make or n8n can learn them. It is marked with the header X-Chatpilot-Test: true.

What is sent

Running an action goes through the same card, Run and log as every action (Actions in connected systems). ChatPilot posts exactly the card's fields as one JSON object, with the header X-Chatpilot-Action naming the action (one address can serve several actions) and a fresh X-Chatpilot-Delivery id. An id or link in the answer is kept in the log. Redirects aren't followed, and plain http:// only works for addresses on this computer or your own network.

A webhook can't be read back, so tickets sent through one aren't followed.

Edit changes a webhook (leave the address empty to keep it); Remove deletes its address and secret.

Checked against ChatPilot 0.1.0b1. Report a problem with this page