Connect Zapier, Make or n8n with webhooks
Every new form message, contact request of the AI assistant, table entry, booking and paid order can go to web addresses of your choice, up to 10 per website, each with the events it takes. With Zapier, Make or n8n it goes on from there to Google Sheets, your CRM, your newsletter or thousands of other apps. Included in every plan, without credits.
Set it up
In Zapier, start a Zap with Webhooks by Zapier and Catch Hook. In Make, add a Custom webhook. In n8n, add a Webhook node for POST. Copy the address it shows.
In frascati, open Cloud in the editor and scroll to Connections. Click Add a webhook, paste the address, give it a name if you like, choose its events and click Add webhook.
Click Send test event. frascati says what the address answered, and the test shows under Deliveries.
Send a form on your published website, or make a test booking in the preview, so Zapier, Make or n8n see real fields to work with.
An address has to start with https:// and be reachable from the internet, and it may not be on frascati itself, like frascati.app, frascati.page or a website's own domain: webhooks go to other services. Each one has its own events and its own secret. Edit changes its address, name or events; Remove stops it and deletes its log. A website sends to 10 addresses at most. To let these tools add entries and bookings to your website too, use the API.
What is sent
- message.created
- A form message from your website, with
pageandformwhen the website said where it came from. - assistant.request
- A contact request the AI assistant took from a visitor: name, email or phone, and what they want. An address that does not take this event but takes form messages gets it as
message.created, as before. - entry.created
- A visitor's entry in a table, or one added through the API (then
sourceisapi). - booking.created
- A new booking or request, also a place in a class or an event or on its waitlist.
- booking.confirmed
- A request you confirmed, or a place someone got from a waitlist.
- booking.cancelled
- A cancelled booking, with who cancelled it,
guestorowner. A date of a class you cancel, or a class you remove, cancels each of its bookings this way. - order.paid
- A paid order from your Stripe checkout.
- test
- Send test event: goes to that one address whatever events it takes, and is not tried again.
Each one is a POST with JSON: id, the event's own id, the same at every address and in every try; event; site, your website's name; projectId; sentAt, when it happened; and data, the message, entry, booking or order itself. A booking has its date, time, service, people, name, email, phone, note, the person of your team it is with and its status, source is owner when you added it in the Cloud tab (then the email can be empty) and api when it came through the API, and test is true when it was made in the preview. A booking of classes and events has kind set to class, the class and className instead of the service, seats instead of people, and the status confirmed, waitlist or cancelled.
{
"id": "evt_8KcQ2m0sV1xR7tL4",
"event": "booking.created",
"site": "Salon Sihl",
"projectId": "cmg7x2k1a0003la08f3hq9c2d",
"sentAt": "2026-10-14T09:12:44.512Z",
"data": {
"id": "cmg7x9d4e0011la08b6n0w1rt",
"service": "cut",
"serviceName": "Haircut",
"date": "2026-10-20",
"time": "10:00",
"minutes": 60,
"people": 1,
"name": "Lena Graf",
"email": "lena@example.com",
"phone": "+41 79 000 00 02",
"note": null,
"fields": {},
"staff": "lea",
"staffName": "Lea",
"status": "confirmed",
"test": false,
"source": "site"
}
}Deliveries, retries and the log
Each event to each address is a delivery. When the address does not answer with a 2xx status within 8 seconds, frascati tries again after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours, 6 tries in all, each with the same body and the same id. Then the delivery is Failed. A redirect, the status 410 and an address on no public network fail at once, since another try would end the same way. When 20 deliveries in a row to one address failed, frascati pauses it: new events are not sent to it, and its deliveries waiting for a try wait. The address shows Paused; fix it in Zapier, Make or n8n, then click Resume, or Send test event: a test that arrives resumes it too.
- Deliveries
- Under Connections, the deliveries of the last 30 days, newest first, by address and by state: Delivered, Retrying with the time of the next try (or waiting while the address is paused), Failed.
- A delivery
- Click one to see every try with its time, the status code your address answered, how long it took and the start of its answer when it was an error, and the body that was sent.
- Send again
- Tries a delivery once more right away, with the same body. Use it after you fixed a Zap or a workflow.
Use id to recognize an event you have already handled: a try can reach you after an earlier one your side did receive but answered too slowly. The log keeps the data sent for 30 days, then deletes it with the delivery.
Check that a call comes from frascati
For developers: every call carries the headers X-Frascati-Event, X-Frascati-Timestamp, X-Frascati-Signature, X-Frascati-Delivery (the delivery in your log) and X-Frascati-Attempt (1 for the first try). The signature is sha256= followed by the SHA-256 HMAC, in hex, of the timestamp, a dot and the raw body, with the address's secret as the key. Each address has its own secret, starting with whsec_: click Secret, then Show and Copy. New secret makes another one, and the old one stops at once.
import { createHmac, timingSafeEqual } from "node:crypto";
// rawBody: the body exactly as it arrived, before JSON.parse
function fromFrascati(rawBody, headers, secret) {
const timestamp = headers["x-frascati-timestamp"];
const expected = "sha256=" + createHmac("sha256", secret).update(`${timestamp}.${rawBody}`).digest("hex");
const given = String(headers["x-frascati-signature"] ?? "");
const fresh = Math.abs(Date.now() / 1000 - Number(timestamp)) < 300;
return fresh && given.length === expected.length && timingSafeEqual(Buffer.from(given), Buffer.from(expected));
}The timestamp is the time of each try, so a check that refuses old calls keeps working for retries.
Webhooks from before
A website that had its webhook before there could be several keeps it: the same address, the same secret, so your check of the signature stays as it is, and the six events it always got. A contact request of the AI assistant still arrives there as message.created, with source set to AI assistant in the message. Choose Requests from the AI assistant under Edit to get those as assistant.request instead.
Something missing or unclear? Write to us.
