Automation · Connect with an API key and webhooks
Retime for Make
Make starts a scenario from a custom webhook. Point a Retime webhook at it, and each booking runs your scenario with the full payload.
What you get
One scenario, many outcomes
Branch on the event type or the guest answers and take a different path for each.
The payload is ready to map
Make reads the sample from the first delivery, so every field appears in the mapping panel.
Two way work
An HTTP module with a personal API key reads or writes Retime data in the same scenario.
Deliveries are repeated on failure
A scenario that is paused or slow does not lose the booking, because Retime tries again.
How to connect Make
Create a custom webhook in Make
Add the Webhooks module, choose Custom webhook, and copy the address.
Add the webhook in Retime
Open Account, then Webhooks, paste the address, and select the booking events.
Send a test
Click Ping so Make receives a sample and learns the data structure.
Add your modules
Map the guest name, the guest email, the start time, and the event type into the next module.
Add an API key for HTTP modules
Create a key under Account, then Integrations, and send it in the Authorization header.
Questions about Make
Is there a Retime app in Make?
Not yet. The custom webhook and the HTTP module cover the same work today.
Why does Make show no fields?
Make learns the structure from the first delivery. Click Ping on the Retime webhook while Make is listening.
Can one webhook feed several scenarios?
Add one Retime webhook for each Make address. A Retime account can hold more than one webhook.
Put Make to work
Create a free account, connect your calendar, and share your first booking link today.