Pre-meeting LinkedIn briefs in Slack for new Calendly bookings

Build me an agent workflow that creates a pre-meeting prospect briefing in Slack every time someone books a meeting on Calendly.

Trigger: a Calendly webhook on the invitee.created event. When the webhook fires, run the agent with the invitee and event URIs from the payload.

Step 1. Pull the booking. Use Calendly's Get Scheduled Event and Get Event Invitee operations so the agent has the invitee's name, email, company, the assigned host (rep), the scheduled start time, and the questions and answers from the intake form (especially the LinkedIn URL if the form captures one).

Step 2. Enrich the prospect through RapidAPI using the Call a Subscribed Hub API operation. Make two calls with the same RapidAPI key, one for the person and one for the company:

Person signal: hit a LinkedIn profile data API on the RapidAPI Hub. Default to Fresh LinkedIn Profile Data (X-RapidAPI-Host: fresh-linkedin-profile-data.p.rapidapi.com), and also call its profile-posts endpoint to fetch posts from the last 60 to 90 days. Pull current role, headline, location, and the recent post list with dates and short text.

Company signal: hit a company lookup API on the RapidAPI Hub for the prospect's company domain. Pull funding stage, headcount, industry, and the latest one or two press mentions.

Record the X-RapidAPI-Host header used for each call so every fact in the brief can be traced back to a source.

Step 3. Synthesize a one-page brief in Slack mrkdwn formatting with these sections: a one-line summary (name, role, company, meeting time), two to three conversation hooks grounded in specific posts with dates, two talking points tied to the company snapshot (recent funding round, headcount growth, product launch), and any risk flags (former competitor, recent job change, tiny team for the deal size). Under each fact, put the source host in small italics so the rep can see which API it came from.

Step 4. Post the brief. Use Slack Bot's Send a Message operation to the assigned rep's prep channel (default #prep, with an editable per-rep override map). Schedule the post a few hours before the meeting start time using the scheduled-message option so the brief lands at a useful moment, not the instant the meeting books. Leave the message open as a thread so the rep can drop in notes.

Edge cases. If the intake form has no LinkedIn URL, skip the LinkedIn profile call and post a lighter brief built from Calendly intake answers plus the company lookup. If a RapidAPI call returns 403 or 429, log the host and response and post a brief that names which data layer is missing so the rep knows what is and is not covered.