This is an enterprise integration and it needs a developer. Here is the honest map — including why most people on this page want a different page.
Start here: are you sure you want Marketing Cloud, and not Salesforce? Most people searching for this want appointments to appear against the Lead or Contact in Salesforce CRM — the object their sales team actually works. That is a different, much easier job, and we wrote it up properly on Bookafy + Salesforce. If that is you, go there; you will be finished in an hour.
Salesforce Marketing Cloud (SFMC) is a different product: journeys, Email Studio, Data Extensions, Contact Builder. You would only want Bookafy talking to it if a booking is supposed to enter or exit a journey. That is a real requirement, it is just an enterprise-shaped one — and it needs someone who can write a little code.
| Zapier triggers | Zapier actions | Also available |
|---|---|---|
| New Appointment New Customer New Appointment Type New User |
Create Appointment Create Customer |
Webhooks + a full open REST API |
Two honest notes before you plan anything. Salesforce is a Premium app on Zapier, so a paid Zapier plan is required for the Salesforce side of any Zap. And Bookafy’s Zapier trigger fires on new appointments only — there is no cancellation trigger and no reschedule trigger. In a marketing-automation context that is not a footnote, it is the design constraint. A journey that cannot hear a cancellation will keep sending.
| Approach | How it works | Our view |
|---|---|---|
| 1. Route through Salesforce CRM | Bookafy → Salesforce (Lead/Contact/Event, via Zapier or the API). SFMC then reads the CRM data it is already synced with, and your journeys entry-criteria off the standard objects. | The one we recommend. No new pipes, no new Data Extension, and the appointment ends up where sales can see it too. If your SFMC is connected to your CRM — and it almost always is — this is the whole job. |
| 2. Bookafy webhook → SFMC Data Extension | Bookafy fires a webhook on booking; a small middleware endpoint (or Zapier Webhooks, or Make) authenticates against SFMC’s REST API and upserts a row into a Data Extension. Journeys entry-source: that Data Extension. | The right build if you genuinely need appointment data inside SFMC and not just in the CRM. Budget developer time — the SFMC auth handshake is the fiddly part, not our side. |
| 3. Direct Zapier into SFMC | Depends entirely on which Marketing Cloud connectors your Zapier account has, and what your SFMC package exposes. | Do not plan a rollout around it. Check what your own account actually offers before you promise anyone a date. |
SFMC journeys are timed, patient and unforgiving. If a booking puts someone into a “you have a consultation on Thursday” journey and they cancel on Tuesday, nothing in the standard Zapier path tells the journey. It will send the Wednesday reminder. It will send the Friday “great to meet you”.
So build the cancellation path first, not last. Point a Bookafy webhook at your middleware, and on a cancellation or a change, upsert the Data Extension row with a status field — booked, rescheduled, cancelled — and use a decision split on it. If you are only going to build one webhook, build that one.
If you are scoping this and want to talk it through with someone who knows both sides, book a call. That is, after all, the thing we make.
Booking is the easy half. Start there and connect the rest at your own pace.
Not natively. Bookafy connects through Zapier, Make, webhooks or its open REST API. The most reliable route is Bookafy into Salesforce CRM, which Marketing Cloud already reads from; the alternative is a webhook that upserts a Data Extension through SFMC’s REST API.
Usually yes. Most people who search for this want the appointment on the Lead or Contact record their sales team works. That is a simpler build and it is covered on the Bookafy + Salesforce page.
Yes for the Salesforce side — Salesforce is a Premium app on Zapier, which requires a paid Zapier plan.
Nothing, unless you build for it. Bookafy has no cancellation trigger in Zapier, so a journey will keep sending. Use a Bookafy webhook to upsert a status field on the Data Extension row and add a decision split on it. Build this path first, not last.
Yes — full white-label under your own brand, domain and emails is available for larger accounts as a paid setup. It is the usual reason enterprise teams choose Bookafy.
Bookafy also connects to 3,000+ apps through Zapier and Make, and offers an open API and webhooks for anything custom.
If you’re weighing up appointment scheduling software, these go deeper:
