Calendly Booking Risk Check with ZeroBounce, Attio, and Slack

Build me an agent workflow that triages every new Calendly booking so my AEs do not waste demo slots on fake or low-intent invitees.

Trigger: Calendly webhook on the invitee.created event. When Calendly fires the webhook, the agent should run with the invitee's name, email, the meeting time, the event type, and the user who owns the calendar.

Step 1. Check the email with ZeroBounce. Call ZeroBounce Validate Email on the invitee's email address. Then call ZeroBounce Get Activity Data on the same address to see if the mailbox has shown recent inbox activity. Keep both results.

Step 2. Decide a risk level. Mark the booking as high risk if any of the following are true: the email status from Validate Email is invalid, the sub-status flags it as disposable or role_based, or Get Activity Data returns no recent activity at all. Otherwise mark it as low risk.

Step 3. Update Attio either way. Use Attio Assert a Record (Upsert) on the People object, matching on email_addresses, to create or update the person with their name, email, and a booking_risk attribute set to either high or low. Always do this step so the AE has CRM context when they open the meeting.

Step 4. If the booking is high risk, also do these two things. First, use Attio Create a Task linked to that person record, assigned to the Attio user that matches the Calendly meeting owner's email, with a short title like "Confirm Calendly booking with <invitee> before prep" and a deadline 30 minutes before the meeting. Second, use Slack Send a Message (via the Slack Bot integration) to ping the AE who owns the calendar. Pick the channel by mapping the Calendly meeting owner to a Slack user and DMing them, or post into a shared #booking-triage channel if I configure one. The Slack message should say who booked, the meeting time, the event type, and one short line explaining which ZeroBounce signal raised the flag (for example: "flagged as disposable" or "no recent inbox activity").

If the booking is low risk, do not send any Slack message and do not create a task. The silent Attio upsert in step 3 is enough.

Use an agent because the Slack copy and the reason line should read naturally and reflect whichever ZeroBounce signal actually fired, instead of a templated one size fits all message.

Additional information

What does this prompt do?

Runs the second a new Calendly invitee schedules a meeting, before the slot ever shows up on a rep's calendar with no context.
Checks the invitee's email against ZeroBounce to see if it is valid, disposable, role based, or has shown recent inbox activity.
Writes a booking risk score onto the matching person record in Attio so the AE has CRM context the moment they open the meeting.
If the email looks fake or low intent, creates an Attio task for the meeting owner and pings them in Slack with the risk reason.

What do I need to use this?

A Calendly account that can send webhooks when a new invitee is created.
A ZeroBounce account with email validation credits.
An Attio workspace where you track people and tasks.
A Slack workspace where your sales team gets alerts.

How can I customize it?

Change the risk rules. Add disposable domains you care about, treat role based addresses as high risk only on enterprise event types, or require a minimum activity window.
Change who gets pinged. Route alerts to a single sales ops channel, DM the AE who owns the calendar, or split by event type.
Change the CRM fields you write. Push the risk reason into a note, a custom attribute, or a list entry instead of a single tag.

Frequently asked questions

Will this cancel the meeting automatically?

No. The agent never touches the booking itself. It only writes context into Attio and sends a heads up in Slack so a human can decide whether to confirm, reschedule, or drop the meeting.

What counts as a high risk booking?

By default, the agent flags invalid emails, disposable inboxes, role based addresses like info@ or sales@, and mailboxes with no recent inbox activity. You can tighten or loosen those rules in the prompt.

Does it run on every Calendly meeting?

Yes, every new invitee triggers the check. If you only want it on certain event types, like demos or enterprise calls, you can scope the agent to those event types when you set it up.

What happens if the email looks legitimate?

The agent silently upserts the person in Attio with a low risk tag so the rep still gets CRM context for the meeting. No Slack alert and no task are created.

Can it work with a different CRM?

Yes. The same pattern works with HubSpot, Salesforce, or Pipedrive. Swap the Attio steps for your CRM when you generate the workflow.