# Add a webhook Action (Zapier, Make, n8n)

> Let your Chirp send details to a Zapier, Make, n8n or Pabbly webhook, without a schema, with the visitor confirming first.

Source: https://www.chirpbuilder.com/help/actions/webhook  
Plans: Essentials, Creator, Business, Academy  
Last checked: 2026-10-27

When you're done, your Chirp can send what a visitor tells it to your automation, once they confirm.

**Who can do this:** the account owner on any plan, and workspace admins and editors.

## Add it

1. In Zapier, Make, n8n or Pabbly, make a "catch hook" or webhook trigger and copy its address.
2. In the editor, open **7. Actions**, click **Add an Action** and choose **Webhook (Zapier, Make,
   n8n)**.
3. Paste the **Webhook address** (1). It must start with https://, with nothing after a ? or #.
4. Fill in **What it does**, like "Add to my email list", and if you like **When to use it
   (optional)**, like "When someone asks to join the newsletter". The AI reads both to decide when to use
   it. Visitors see them too, on the card that asks them to confirm.
5. Under **Fields** (2), list what the webhook should get. Each field has a name (letters, numbers and
   _, starting with a letter or _), a type (**Text**, **Number**, **Whole number** or **Yes/no**), what it is for the AI, and
   whether it's **Required**. Up to 30 fields.
6. Click **Add webhook** (3).

![The Webhook (Zapier, Make, n8n) tab: a Zapier catch hook address (1), What it does set to Add to the seed swap list, the fields it receives (2), starting with email, and Add webhook (3).](https://mjmtbasmrtksluvlnema.supabase.co/storage/v1/object/public/help-media/web-optimized/actions/webhook/SS-ACT-020-01__webhook-form__essentials__desktop__v01.webp?v=0a5243f78c)

Then publish: visitors get it once you click **Publish changes**.

## What happens in a chat

When a visitor asks for it, the Chirp fills in the fields from the conversation and shows a card with
what will be sent. Nothing is sent until they click **Confirm** (or **Yes, do it** for a delete). See
[What visitors see when a Chirp wants to make a change](https://www.chirpbuilder.com/help/actions/confirmation-card).

The webhook gets a POST with a JSON body holding only the fields you listed.

## Good to know

- **Words matter.** The name, "When to use it" and the webhook address itself are read for certain
  words. Words like buy, pay, payment, checkout or refund make it look like a payment: the webhook is
  added, but as **Not supported yet**, and it can't run. Words like remove, delete, cancel or
  unsubscribe make it a delete, which always asks first. So an n8n address ending in /cancel-booking is
  a delete.
- **Asking first is on.** You can switch **Visitors confirm first** off for it, except for a delete: see
  [Choose operations, and when visitors confirm first](https://www.chirpbuilder.com/help/actions/operations-and-confirming).
- **To send leads** from a lead form to Zapier or Make, use the lead form's own webhook instead: see
  [Send leads to Zapier or a webhook](https://www.chirpbuilder.com/help/collections-leads/lead-webhooks).

## If it doesn't work

- **"Paste the full webhook address, starting with https://."** or **"The webhook address must start
  with https://."**
- **"Use the webhook address without anything after a ? or #."**
- **"That host name only works inside a private network."**, **"That address points to a private
  network."** or **"That isn't a valid public host name."**: use the address your automation service
  gave you.
- **""…" can't be a field name. Use letters, numbers and _ (no spaces)."**
- **"The field "…" is listed twice."**
- **"A Chirp can have up to 10 Actions. Remove one first."**