Pause Reply.io sequences when a Calendly meeting is booked

Build an agent workflow that fires whenever a prospect books a meeting on Calendly, then silences any cold outreach to them in Reply.io and reflects the booking in HubSpot.

Trigger: a webhook from Calendly on the invitee.created event. The webhook payload includes the invitee's email, name, the scheduled event URI, the event type, and the meeting start time. If any of those fields are missing from the payload, call Calendly's Get Event Invitee to pull the full record before continuing.

In Reply.io, find the contact by the invitee's email. Use List Contacts (search by email) to locate the contact record and pull their contactId. If the contact is enrolled in a sequence, use Get Sequence Contacts (Extended) to identify the active sequenceId they are currently on. Then call Set Contact Status with status MeetingBooked and pass that sequenceId so Reply.io pauses every remaining step in the cadence (email, LinkedIn, calls, SMS, tasks). Note: Reply.io requires a sequenceId for sequence-scoped statuses like MeetingBooked, so the lookup is necessary, not optional.

If the email is not found in Reply.io, skip the Reply.io steps and continue. Do not fail the workflow.

In HubSpot, run Search Contacts by email to find the contact. If found, call Update Contact to record the meeting time and the Calendly event type on the contact properties. Then call Create Note associated to that contact summarizing who booked, the event type, the meeting start time in the contact's local time zone if available, and which Reply.io sequence sourced the meeting (sequence name plus id). The note should make it easy for the team to credit the right campaign for the booking.

If the contact does not exist in HubSpot, create the note attribution context in plain text within the workflow log instead, but do not create a new contact unless the operator explicitly opts into that during setup.

Keep the workflow tight: one Calendly booking in, Reply.io paused (when applicable), HubSpot updated, sequence attribution captured. No other side effects.

Additional information

What does this prompt do?

Listens for new Calendly bookings and instantly stops further cold emails to that prospect in Reply.io.
Marks the contact as Meeting Booked in the right Reply.io sequence so they drop out of the cadence cleanly.
Updates the matching HubSpot contact with the meeting time and event type so your CRM mirrors reality.
Adds a HubSpot note crediting the Reply.io sequence that sourced the meeting, so the right campaign gets the win.

What do I need to use this?

A Calendly account where you can turn on outgoing booking notifications.
A Reply.io account with the sequences you want to silence when meetings get booked.
A HubSpot account where the prospect's contact record lives.

How can I customize it?

Limit it to bookings on specific Calendly event types, such as demos or discovery calls only.
Change the wording of the HubSpot note, for example to flag which rep owns the meeting.
Decide what should happen if the email is not in Reply.io. The default is to still update HubSpot.

Frequently asked questions

Will this actually stop the next email in the Reply.io sequence?

Yes. As soon as the meeting is booked, the contact is marked Meeting Booked on their active sequence, which pauses all further steps. No more cold emails, calls, or LinkedIn touches go out.

What if the person who booked is not in Reply.io?

That is fine. If we cannot find them in Reply.io, we skip the pause step and still update HubSpot with the meeting details so your CRM stays accurate.

How does it know which Reply.io sequence to credit?

We look up the prospect's active sequence in Reply.io and reference it in both the status update and the HubSpot note, so attribution lands on the campaign that actually sourced the meeting.

Does this work for any Calendly event type?

By default, yes. It runs on every new Calendly booking. You can narrow it to specific event types like demo calls or discovery calls during setup.

What gets written to HubSpot?

We update the contact with the meeting time and event type, then add a timestamped note summarizing who booked, when, and which outbound sequence they came from.