Create an endpoint
Use an HTTPS endpoint owned by your automation or application. For Make, this will normally be a custom webhook URL generated by your scenario.
Choose event types
Subscribe only to the events your workflow needs, such as reservation created, reservation updated, guest readiness changed or property availability changed. Avoid an everything feed when a narrow subscription will do.
Verify the signature
Production Zuesie webhook deliveries will include a signing mechanism so your endpoint can prove the event came from Zuesie. Do not build production automations around unsigned payloads.
Return quickly
Acknowledge valid events quickly, then do slower work asynchronously. Delivery retries should not accidentally create duplicate bookings or duplicate messages, so downstream actions must be idempotent.
Use delivery history
Zuesie will keep webhook delivery status and retry information visible so failed automations can be diagnosed without guessing what was sent.
Need help?
Early Zuesie customers can use the Support section inside the PMS to talk directly to Mara and the Zuesie team.