Connect any booking system with Zapier or Make

Before you start

1. In Rumore, open Connections and find the card called Any booking system.
2. Press Turn on the booking link, then copy the booking link and the secret. The secret is shown only once, so keep the page open until your zap or scenario is saved.

Lost the secret? Press Replace secret on the same card. The old one keeps working for 24 hours, so nothing is dropped while you update it.

If your booking system can only start a zap when a booking is made, that works too. Send the visit with its times, and if the booking is later cancelled, send it again with status cancelled and the same externalId.

Zapier

1. Make a zap that starts when a booking is finished in your booking system.
2. Add the step Webhooks by Zapier, choose POST, and paste the booking link as the URL.
3. Set Payload Type to JSON and map the fields below.
4. Under Headers, add Authorization with the value Bearer, a space, then your secret.

Webhooks by Zapier needs a paid Zapier plan.

Make

1. Start your scenario with your booking system's finished-booking trigger.
2. Add the HTTP module Make a request, method POST, and paste the booking link as the URL.
3. Add a header named Authorization with the value Bearer, a space, then your secret.
4. Set the body type to JSON and map the fields below.

Fields to send

• name: the guest's name (required)
• email or phone: at least one. Write the phone with its country code, like +4512345678.
• visitAt: when the visit started, with its timezone, like 2026-10-05T19:30:00+02:00 (required)
• endAt or durationMinutes: when it ended. If neither is sent, the visit counts as 90 minutes.
• externalId: the booking's id in your system, so a repeat is never counted twice
• status: completed, no_show or cancelled. Left out, it means completed.

An example you can copy

This is one finished visit, the way Rumore expects it. Map your booking system's fields onto these names. Only name, visitAt and an email or phone are required.

{
  "name": "Dana Levi",
  "email": "dana@example.com",
  "phone": "+4520123456",
  "visitAt": "2026-10-05T19:30:00+02:00",
  "endAt": "2026-10-05T21:00:00+02:00",
  "externalId": "booking-1042",
  "status": "completed"
}

Check the link from a terminal

To check the link and secret before you build anything, paste this into a terminal and put your own booking link and secret in place of the capitals. The visit in it is months old, so Rumore answers too_old and nobody is asked. It does add Test Guest to your Contacts.

curl -X POST "YOUR_BOOKING_LINK" \
  -H "Authorization: Bearer YOUR_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"name":"Test Guest","email":"test@example.com","visitAt":"2026-01-15T12:00:00Z","durationMinutes":60,"externalId":"rumore-test-1"}'

What happens after a visit arrives

• The guest is asked 3 hours after the visit ends, inside your sending hours. If you set your own delay in Rumore, yours is used.
• Anyone who has told you not to contact them is never asked, and nobody is asked again too soon after their last request.
• A visit sent as cancelled or no_show is kept, and nobody is asked. Send the same externalId again with the new status and an ask that is still waiting is stopped.
• Rumore never reads consent or marketing fields from your booking system, so leave them out.

What Rumore answers

Zapier and Make show this answer in each run's history. It is the first place to look if visits are not arriving.

• 202 accepted The visit is in. If it qualifies, the guest is asked 3 hours after it ended.
• 202 duplicate Rumore already had this exact visit, so nothing changed.
• 202 too_old Kept in the guest's history. The visit ended more than 7 days ago, so nobody is asked.
• 401 The secret is wrong, or the booking link is turned off.
• 422 A field is missing or cannot be read. The answer names the field.
• 429 Too many visits in a short time. Wait a minute and send it again.