Hunter pre-call briefs in Slack for new Calendly bookings

Build an agent workflow that produces a pre-meeting research brief in Slack the moment a prospect books a meeting on my Calendly, so I never walk into a discovery call cold.

Trigger: Calendly webhook on the invitee.created event. When the workflow fires, read the invitee's email, name, the Calendly event type (discovery call, demo, intro, etc.), the scheduled start time, and the meeting host from the booking payload. Derive the company domain from the part of the email after the @.

Short-circuit guard: if the invitee email is on a free webmail domain (gmail.com, outlook.com, hotmail.com, yahoo.com, icloud.com, proton.me, aol.com), skip the rest of the workflow. Hunter cannot return useful firmographics for personal addresses and the brief would be empty.

Step 1 (Hunter): call Enrich Person and Company (Combined Enrichment) with the invitee's email. Capture the person's full name, title, seniority, LinkedIn and Twitter handles, and the company's name, industry, headcount, location, description, and any funding/tech signals returned.

Step 2 (Hunter): call Search Emails by Domain on the invitee's company domain. Filter to executive and senior seniorities so you get the rest of the buying committee, not every junior contact. Pick the three contacts most likely to matter for a deal at that company (founders, C-level, VPs, heads of the relevant function based on what we sell). Capture each one's name, title, and verified status.

Step 3 (write the brief): compose a concise Slack-friendly message in Slack mrkdwn formatting (use *bold*, not **bold**) with these sections:

• Who I'm meeting: invitee name, title, company, and a one-line read on their seniority and likely buying role.

• Company snapshot: industry, headcount band, location, and any funding or growth signal worth knowing.

• Why they likely booked: a one-line hypothesis inferred from their title plus the Calendly event type (e.g. "VP RevOps on a demo call usually wants to see reporting and integrations").

• Three talking points tailored to their role and company.

• Three other senior people at the account worth name-dropping or following up with, formatted as name + title.

• Footer line with the Calendly event type and the meeting start time in the host's timezone.

Keep it under ~250 words so it fits on one screen. No filler, no "I hope this helps".

Step 4 (Slack Bot): post the brief by calling Send a Message. Default to a dedicated channel I will configure (something like #pre-call-briefs). If I tell you to DM the meeting host instead, use Open a Conversation with the host's Slack email/user, then Send a Message into the returned conversation id.

Edge cases to handle gracefully: if Hunter returns no person match, still post a shorter brief using whatever company data we got and flag "no person match". If Hunter returns no domain results either, post a one-line note saying the booking arrived but enrichment came up empty (do not silently drop it). If Hunter is rate-limited or out of credits, surface that as a Slack message so I know to act.

Make the destination channel, the seniority filter, the personal-domain skip list, and the choice of channel-post vs DM-the-host all easy to edit at the top of the workflow.