Skip to content
Inbound webhooks logo

Automation & developer

Connect bookings to anything with Inbound webhooks.

An inbound webhook is a URL you post to, so another system can push a lead or a booking into udaybooking. Not every system needs a dedicated connector. A booking event and a place to send it covers most of what a team actually wants automated.

What is switched on depends on your plan and industry pack. Ask us to confirm before you build a process on it.

Inbound webhooksBooking workflow
  1. 1Booking event fires
  2. 2Inbound webhooks scenario runs
  3. 3Your system updated

Illustrative flow, not a screenshot of a connected account.

In the udaybooking connector catalogueBrowse the full catalogueHow we handle your data

What Inbound webhooks brings to your booking workflow

01

Events, not exports

A booking, a reschedule or a cancellation can start work in Inbound webhooks the moment it happens.

02

The long tail, covered

The internal tool nobody built a connector for is reachable the same way as the popular one.

03

Your logic stays yours

What happens after the event is defined in Inbound webhooks, where your team can change it without waiting for us.

How it works

Three steps to a connection you can trust. Follow the screens in your own account for the exact wording.

  1. 1

    Choose the trigger

    Which booking events matter: created, rescheduled, cancelled, completed.

  2. 2

    Build the automation

    Set up the Inbound webhooks scenario that receives the event and does the work.

  3. 3

    Test both paths

    Check a success and a failure, so you know what a broken run looks like.

Where Inbound webhooks sits in the catalogue

Inbound webhooks is part of the core stack — the baseline every udaybooking account can turn on, whatever it sells.

Browse the full catalogue

Listed under

  • Lead capture
  • Automation

Where this connection helps

Lead capture

The catalogue files Inbound webhooks under lead capture, one of the jobs that decides when an appointment should be offered, confirmed or moved.

Automation

The catalogue files Inbound webhooks under automation, one of the jobs that decides when an appointment should be offered, confirmed or moved.

Inbound webhooks questions

  • Do I need a developer?

    For Inbound webhooks, usually not — it is built for people who can describe the workflow. Custom receivers are a developer job.

  • What do the events contain?

    Ask us for the current event list and payload before you build against it, rather than inferring fields from an example.

  • Is Inbound webhooks available on my plan?

    Inbound webhooks is in udaybooking's connector catalogue, and what is switched on depends on your plan and the industry pack you run. Ask us to confirm it for your account before you build a process around it.

Start scheduling with Inbound webhooks.

Set up your booking page, connect what you already use, and let people pick a time that works.