Connections
Send form messages, bookings and orders to Zapier, Make or n8n
Every form message, table entry, booking and paid order of your website goes as signed JSON to a webhook in Zapier, Make or n8n, and on to Sheets or a CRM.
Key facts
- What it is
- One webhook address per website. frascati sends each event there as a POST request with JSON.
- Events
- Form messages (message.created), entries from visitors (entry.created), new, confirmed and cancelled bookings (booking.created, booking.confirmed, booking.cancelled) and paid orders (order.paid)
- Works with
- Zapier (Catch Hook), Make (Custom webhook), n8n and any other service that takes a JSON POST over https
- Body
- event, site, projectId, sentAt, and data with the message, entry, booking or order
- Signature
- The header X-Frascati-Signature holds sha256= and an HMAC SHA-256 of the timestamp from X-Frascati-Timestamp, a dot and the body, made with your website's secret
- Delivery
- Right after the event. Your address has 8 seconds to answer. After a server error or no answer, frascati tries once more 3 seconds later.
- Test
- A button sends a test event and shows the status code your address answered
- Address
- https only, reachable from the internet, without a user name or password in it
- Plans
- Every plan, no credits. See pricing
How it works
- 01
Create a webhook trigger
In Zapier, start a Zap with “Catch Hook”. In Make, start a scenario with “Custom webhook”. In n8n, start a workflow with a webhook trigger. Copy the address it gives you.
- 02
Paste it in the Cloud tab
Paste the address under Connections in the Cloud tab and send a test. frascati shows what your address answered, and the secret for checking the signature is ready to copy.
- 03
Events go out on their own
From then on, each form message, visitor entry, booking change and paid order goes to that address. Visitors notice nothing: frascati sends the event after their form, booking or payment is done. In Zapier, Make or n8n you pass it on to Google Sheets, your CRM or your newsletter.
What it does not do
- One address per website. To reach several tools, split the events in Zapier, Make or n8n.
- No filter in frascati: every event goes to the address, and you filter by the field event.
- Connections only send. Nothing comes back from Zapier, Make or n8n into your website.
- No log of deliveries and no later resend. If both tries fail, the event is not sent again, but the message, entry, booking or order stays saved in frascati.
- Changes you make to a table yourself are not sent, only new entries from visitors.
- No direct connection to Google Sheets, a CRM or a newsletter tool. They go through Zapier, Make or n8n.
Questions
- Which events does frascati send?
- A new form message, a new entry from a visitor in a table, a new booking, a booking request you confirmed, a cancelled booking and a paid order. Each call names its event, for example booking.created.
- How do I check that a call comes from frascati?
- Each call carries the header X-Frascati-Signature: sha256= followed by an HMAC SHA-256 of the timestamp from X-Frascati-Timestamp, a dot and the raw body, made with your website's secret. Compute the same value and compare.
- Can I send bookings to Google Sheets or my CRM?
- Yes, through Zapier, Make or n8n: they receive each booking from frascati and pass it on. frascati has no direct connection to Sheets or a CRM.
- What happens when my webhook address is down?
- frascati waits 8 seconds for an answer. After a server error or no answer it tries once more 3 seconds later, then stops. The message, booking or order stays saved in frascati.
- Do connections cost extra?
- No. They are part of every plan and use no credits. Zapier, Make and n8n are separate services.
Your website, about two minutes from now
3 days free with a card, then from $12 a month. The plan starts automatically unless you cancel.