Every booking in the CRM once: Calendly into monday.com and Close without duplicates
Two Make scenarios, built for two businesses, take every Calendly booking into the CRM without creating duplicates. One, for monday.com, handles bookings and cancellations, normalises phone numbers and upserts into the right board for each event type. The other, for Close, is the lean version: look the invitee up, and create a lead only if none exists.
Where this applies
Coaches, consultants, recruiters and any business that takes calls through an online booking page and keeps its contacts in a CRM.
- upsert branches in the monday.com version
- 8
- operations for a typical booking
- 7
- CRMs, one pattern
- 2
The problem
A booking page is often the front door: a discovery call, a recruiting conversation, a consultation. Every booking should leave a contact in the CRM, and native integrations tend either to create a new record each time or to sit behind a higher plan.
The person who books twice, or types their phone number differently the second time, should still be one record. And a cancellation should change the record, not leave a booked call on it that will never happen.
What we built
Created or cancelled
The monday.com scenario watches booking events and routes first on whether the booking was created or cancelled, so each kind of event can change the record in its own way.
Normalise before you match
Phone numbers are parsed into international E.164 form before anything is searched, and the booking-form answers are parsed into fields. Two bookings with the number typed differently then match the same contact.
One branch per event type
A second router splits by event type, four of them, each with its own board. Every route searches its board by column value and branches again: update the item it found, or create one. Across created and cancelled that is eight upsert branches, in about forty modules.
The lean version
The Close scenario does the minimum, safely: it lists the booking's invitees, searches Close for a matching lead, and a filter lets the create through only when none is found. Four modules, no duplicates.
The outcome
Both scenarios run on every booking. The monday.com version handled a recent booking in seven operations and two seconds, and used 19 credits in the seven days to 21 October 2026.
The Close version used 23 credits in the same seven days, with bookings arriving steadily through the month.
Where it stops
Matching is only as good as its key: a person who books with a different phone number or email becomes a second contact. The Close version creates leads but does not update an existing one or handle cancellations.
Built with
- Make.com
- Calendly
- monday.com
- Close CRM
Patterns used
- Search before create
- Normalise before matching
- Route by event type
- Filter as the duplicate guard
Page copy drafted with AI assistance. Skofi is accountable for it. Editorial policy
Have something shaped like this?
If any part of the above resembles a problem you are living with, a short call is the fastest way to find out whether it is the same problem underneath.
What happens on the call
- 15 minutes, no deck
- We map the process on the call
- A written scope, or an honest no