Automate with Zapier

Zapier connects Your Day Schedule to just about everything else — add a booking to a Google Sheet, ping a Slack channel when someone pays, create a CRM contact for every new client. One webhook URL, no code.

Connect Zapier

You'll need a Zapier account. Note that Webhooks by Zapier is one of Zapier's premium features — check that your Zapier plan includes it.

Step 1 — create a Catch Hook in Zapier

1. In Zapier, click Create Zap.
2. For the trigger, choose Webhooks by Zapier → Catch Hook.
3. Zapier shows a webhook URL starting with https://hooks.zapier.com/hooks/catch/… — copy it.

Step 2 — paste it into Your Day Schedule

1. Open Settings → Integrations and click Connect on the Zapier card.
2. Paste the webhook URL and click Connect Zapier.
3. We immediately send a test event to your hook — open your Zap's task history in Zapier and you'll see it, with every field laid out so you can map them into your next step.

Only real hooks.zapier.com URLs are accepted — if the connect button complains, double-check you copied the Catch Hook URL, not the Zap's page URL.

What events are sent

Every event arrives as flat JSON: { event, occurred_at, data }. The event field tells you what happened:

• booking.created — a new booking was confirmed (free bookings on creation; paid bookings once payment completes).
• booking.rescheduled — a booking moved to a new time.
• booking.cancelled — a booking was cancelled, by you or the client.
• client.created — someone booked you for the first time and got a client record.
• payment.received — a client paid for a booking (card payments; package-credit redemptions don't fire this, since no money moves at booking time).

All five events go to the same webhook URL. To react to just one kind, add a Filter step in your Zap: only continue if event exactly matches booking.created — then duplicate the Zap for other event types.

Delivery is fire-and-forget: a slow or unreachable Zap never delays or blocks a booking. There's no retry queue — if Zapier is down at that moment, that one event is skipped.

Build your first Zap

The classic starter — every booking in a spreadsheet:

1. Trigger: Webhooks by Zapier → Catch Hook (connected above).
2. Test the trigger — pick the sample event we sent when you connected.
3. Optional: add a Filter for event = booking.created.
4. Action: Google Sheets → Create Spreadsheet Row, mapping the booking fields to columns.
5. Turn the Zap on.

Other favorites: Slack message on payment.received, CRM contact on client.created, a follow-up email sequence on booking.cancelled.

If something's off

The test event never arrived

Check the Zap's task history in Zapier (not the editor) — Catch Hook events appear there even while the Zap is off. If it's truly empty, reconnect in Settings → Integrations and paste the URL again; a fresh test event fires on every connect.

Real events stopped flowing

• Confirm the Zapier card still shows Connected under Settings → Integrations.
• If you rebuilt the Zap, the Catch Hook URL changed — reconnect with the new URL.
• Remember there's no retry: events during a Zapier outage don't backfill.

I want different events in different Zaps

One URL receives everything — that's by design. Use a Filter step per Zap (or Zapier's Paths) to split by the event field.

Disconnecting

Click Disconnect on the Zapier card. Events stop immediately; your Zap and its history stay in Zapier untouched.

Still stuck? Email support@yourdayschedule.com — we answer quickly.