Integrations
Webhooks
Send signed booking events to your CRM, accounting or automation tools (Zapier, Make, n8n). Several endpoints, retries for 3 days, a delivery log with resend.
Who it's for
Why operators use Webhooks
Operators connecting Tourtify to a CRM, accounting software or automation tools such as Zapier, Make or n8n.
Highlights
- Signed booking events, so your systems can trust them
- Several endpoints at once
- Automatic retries for 3 days
- A delivery log with resend
- Failure alerts to the address you choose
Your systems, told the moment something happens
Webhooks send an HTTP request to an address you choose whenever something happens in Tourtify: a booking is created, confirmed, fully paid, changed or cancelled, a checkout expires unpaid, a refund is sent, a reminder goes out or a new enquiry arrives. Your CRM, spreadsheet automation, accounting tool or own software hears about it straight away, without polling.
You can add several endpoints, each with its own events and signing secret. A typical setup sends confirmed and cancelled bookings to a CRM, fully paid bookings to an operations tool, and new enquiries to a team chat through an automation service.
Built on Standard Webhooks
Every request follows the Standard Webhooks specification: a JSON body with the event type, a timestamp and the data, and three headers, webhook-id, webhook-timestamp and webhook-signature. The signature is an HMAC-SHA256 of the id, timestamp and body with your endpoint's secret, so your receiver can prove the request came from Tourtify and hasn't been replayed. Libraries for the specification exist for most languages.
Secrets can be rotated without downtime: during a rotation each request carries signatures made with both the old and the new secret, so you can update your receiver at your own pace.
Delivery you can rely on
Delivery is at least once. If your server is down or returns an error, Tourtify retries with exponential backoff for about three days. Each event has a stable id, so your receiver can safely ignore a duplicate. Every attempt is logged with the request, the response status and body, and how long it took, which makes debugging a failing integration a matter of minutes.
If an endpoint keeps failing for the whole retry period, it is switched off and the owner gets an email, so a broken receiver never goes unnoticed. Requests are only sent to public addresses, never to private networks.
Setting up Webhooks
- 1Switch on Webhooks. Open Plugins in your console and turn it on.
- 2Add an endpoint. Enter the HTTPS address of your receiver and a description.
- 3Choose events. Pick the events it should get. New endpoints start with booking created, confirmed, fully paid and cancelled.
- 4Verify signatures. Copy the signing secret into your receiver and check the webhook-signature header on every request.
- 5Send a test and watch the log. Trigger a test booking and read each attempt's response in the delivery log.
Settings
What you can set up
Webhooks works out of the box with sensible defaults. These are the choices you can make, straight from your console.
Alerts
- Send failure alerts to
- When an endpoint keeps failing for 3 days we switch it off and email this address. Leave empty to email the business owners.
Integrations
How integrations plugins fit in
Integration plugins connect Tourtify to the rest of your business: CRMs, accounting, automation tools and your own software.
- 1
Switch it on
Open Plugins in your console and turn it on. No code and nothing to install.
- 2
Make your choices
Adjust the settings to match how your business works, or keep the defaults.
- 3
It works everywhere it should
Your website, checkout, emails and console pick it up straight away.
Related
More integrations integrations
Public API
Connect your own systems: read tours and live availability, price and create bookings, and sync every booking into your CRM, accounting or BI tools. API keys with scopes, an OpenAPI description, and webhooks for changes as they happen.
AI app connections (MCP)
Connect ChatGPT, Claude, Cursor, VS Code or any MCP app to your business and ask in plain words: what’s on tomorrow, who still owes a balance, how sales compare with last month. Each person signs in and chooses what the app may see; every call uses their own permissions and appears in the activity log.
FAQ
Webhooks: questions
Can I use webhooks with Zapier or Make?
Yes. Use their webhook trigger's address as an endpoint and choose the events to send.
What happens if my server is down?
Tourtify retries for about three days with growing gaps between attempts. Nothing is lost while your server comes back.
How do I avoid processing an event twice?
Store the webhook-id of each event you process and skip any you have already seen.
Which plans include Webhooks?
Webhooks is available on Scale, at no extra cost.
How do I switch on Webhooks?
In your Tourtify console, open Plugins, find it in the list and switch it on. Its settings open straight away, and you can switch it off again at any time.
Do I need a developer?
Only to build the system on the other side. Inside Tourtify, everything is set up from the console.
Does Webhooks work with my other plugins?
Yes. Every plugin is built and maintained by Tourtify, so they work together: discounts, deposits, vouchers and fees all add up correctly at checkout.
Start selling tours direct
Try Tourtify free for 30 days. Add your tours, pick a theme and take your first booking today.