Zapier and Make

Before you start

• The webhook is part of the Pro and Agency plans.
• You need an account with Zapier or Make. In Zapier, Webhooks by Zapier comes only with its paid plans, not with the free one. Make has plans and limits of its own.

Zapier

1. In Zapier, create a Zap (an automation). For its trigger choose Webhooks by Zapier, for the event Catch Hook, and press Continue. Leave Pick Off A Child Key empty and press Continue again.
2. On the Test tab Zapier shows the address of your webhook. Press Copy.
3. In the Beacel dashboard open Alerts. Under Connect more choose Webhook (when you already have one, press Add recipient on its card), paste the address into Endpoint URL and press Add alert.
4. Beacel shows a signing secret once. Zapier does not need it, so press I have saved it.
5. In the ... menu of the new webhook choose Send a test. Back in Zapier press Test trigger: the test lead shows up with all its fields.
6. Add the step that should happen with each lead, for example the Google Sheets row below, and press Publish. From then on every new lead starts the Zap.

Make

1. In Make, create a scenario. As its first module add Custom webhook from the Webhooks app.
2. Next to Webhook press Add and type a name in Webhook name, for example Beacel. Leave API Key authentication empty, because Beacel cannot send that key. Press Save and copy the address Make shows.
3. In the Beacel dashboard open Alerts. Under Connect more choose Webhook (when you already have one, press Add recipient on its card), paste the address into Endpoint URL and press Add alert. Make does not need the signing secret either: press I have saved it.
4. In Make press Run once, so the module waits for a message. Then in Beacel choose Send a test in the ... menu of the new webhook. Make learns the fields of a lead from this test.
5. Add the module that should act on each lead, for example the Google Sheets row below. A new scenario starts switched off: turn it on with the switch on the scenario's page.

Example: each lead as a row in Google Sheets

Write the column names in the first row of the sheet, for example Name, Contact, Interest, Details, Website and Chat. Both tools read the columns from that row.

• In Zapier, choose Google Sheets as the app of the next step and Create Spreadsheet Row as its event, then pick the spreadsheet and the sheet.
• In Make, add the Add a Row module of Google Sheets, pick the spreadsheet and the sheet, and set Table contains headers to Yes.

Then give each column a field of the lead. Zapier and Make list the fields of the test lead together with their values, so you can tell them apart. In Beacel's message they are these:

What Beacel sends

One message for each new lead, as soon as the visitor has left their details. A test lead from the dashboard has an id that starts with test-.

{
  "event": "lead.created",
  "version": 1,
  "lead": {
    "id": "k3x9Qw1pZ8aB",
    "name": "Maria K.",
    "contact": "+370 600 00000",
    "interest": "Trial lesson",
    "details": "Our son is 7. Can he start in September?",
    "lang": "en",
    "source": "chat",
    "created_at": 1762790400000
  },
  "site": "yourbusiness.com",
  "conversationUrl": "https://beacel.com/dashboard?bot=abc123#conversation=xyz789"
}

Every field is described on the Webhook page for developers.

When leads do not arrive

The Alerts tab lists the recent deliveries, and a failed one shows its error. Beacel tries once more after about 30 seconds.

• In Zapier the Zap must be published; in Make the scenario must be switched on.
• Make switches off a webhook that has not been part of any scenario for more than 5 days, and turns new messages away while its queue is full.
• A new trigger in Zapier or a new webhook in Make has a new address. Put it into Beacel with Edit in the ... menu of the webhook.
• Keep the address private: anyone who has it can send data to your Zap or scenario. If it leaks, create a new trigger or webhook and change the address in Beacel.