Save Calendly bookings to Google Contacts with a prep brief

Build me an agent workflow that fires every time someone new books a meeting with me on Calendly, so I open my inbox before the call and have both the contact saved and a clean prep brief waiting.

Trigger: a Calendly webhook on the invitee.created event. Use the Calendly Create Webhook Subscription operation to set the subscription up at deploy time, scoped to my user or organization. The webhook payload gives you the invitee name, email, scheduled event URI, and event type. If you need more detail than the payload provides (timezone, questions and answers, tracking fields, cancellation policy, etc.), call Calendly Get Event Invitee with the URI from the payload.

Step 1, look the invitee up in Google Contacts. Call Search Contacts with the invitee's email address. Remember the People API quirk where you have to send a warmup search first with an empty query before the real search will return results. If the search returns a person whose email matches the invitee, treat them as already saved and skip to step 3.

Step 2, if no match was found, call Google Contacts Create Contact with the invitee's full name (split into given and family names when possible), their email address, a biographies entry that reads "Booked via Calendly: <event type name> on <booking time in my timezone>", and a membership in a label called "New Calendly Booking". If that label does not exist yet, create it first via Create Contact Group and then attach the new contact to it.

Step 3, research the invitee on the open web. Use their name plus the email domain (e.g. jane@acme.com means research "Jane Smith" at acme.com). Pull together a short profile: who they are and their current role, what their company does and roughly how big it is, anything publicly visible that's relevant context for the meeting (recent funding, product launches, news, mutual connections, prior interactions, etc.), and any obvious risks or hooks for the conversation. Treat the email domain as the primary signal for the company and confirm with a web search; ignore generic personal domains like gmail.com, yahoo.com, or outlook.com and just research the person instead.

Step 4, draft a one-page prep brief in clean HTML so it renders nicely in Gmail. Structure it as: meeting header (invitee name, company, event type, scheduled time in my timezone), a two to three sentence "who they are" paragraph, a "what their company does" paragraph, three to five "what I should know going into the call" bullets, and a short "suggested talking points or questions" section. Keep it factual and tight, no fluff.

Step 5, send the brief to my own email address using Gmail Send a Message. Subject line: "Prep brief: <invitee name> (<company>) — <event type> at <time>". Set the From address to my connected Gmail account, plain HTML body, no attachments. Cite any sources you used inline in the brief so I can click through if I want to dig deeper.

Other behavior: if the Calendly event is rescheduled or cancelled later, do nothing in this workflow (a separate workflow can handle that). If web research turns up nothing credible, still send the brief but make it clear the agent could not find public info and lean on whatever the invitee shared in the Calendly intake questions. Log every run with the invitee email, event type, and whether the contact was newly created or already existed.

Ask me at setup time for: (1) the destination email address for the brief, defaulting to my connected Gmail address, (2) whether to apply the "New Calendly Booking" label or a different label name, and (3) optionally an event-type allowlist if I only want this to run for specific Calendly event types (e.g. only discovery calls, not internal 1:1s).