Calendly to Slack pre-meeting LinkedIn briefs via RapidAPI

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.

Additional information

What does this prompt do?

Watches your Calendly account for new bookings and grabs the invitee's name, email, company, and any LinkedIn URL captured on the intake form.
Pulls the prospect's current role, headline, and posts from the last 60 to 90 days, plus the company's funding stage, headcount, and recent press.
Synthesizes a one-page brief with two to three conversation hooks grounded in specific posts, talking points tied to the company snapshot, and any risk flags.
Posts the brief to the rep's prep channel in Slack a few hours before the meeting and opens a thread so the rep can drop in notes.

What do I need to use this?

A Calendly account with permission to receive booking notifications.
A RapidAPI account with a subscription to a LinkedIn profile data API and a company lookup API of your choice.
A Slack workspace with a channel (or per-rep channels) where the briefs should land.

How can I customize it?

Route each rep's briefs to their own prep channel, or send everything to one shared sales channel.
Change how far ahead of the meeting the brief arrives. Some teams want it the moment a meeting books, others want it the night before.
Swap which LinkedIn or company-data APIs the brief draws from so you can mix and match providers as quality and pricing change.
Adjust the lookback window for recent posts and how many conversation hooks or risk flags the brief includes.

Frequently asked questions

What if the prospect did not share their LinkedIn URL on the booking form?

The brief falls back to whatever Calendly captured (email, company, intake answers) and still runs the company lookup for funding stage, headcount, and recent press. You get a useful one-pager, just lighter on the personal signal layer.

How does the workflow know which Slack channel each brief should go to?

You can map each Calendly host to their own prep channel, or set one shared channel for the whole team. Both setups take about a minute to wire up when you first connect Slack.

Can the brief arrive earlier or later than a few hours before the meeting?

Yes. You pick the offset. Some teams want it the moment a meeting books, others want it 24 hours out, and others want it queued for one hour before the call.

Why use RapidAPI instead of a dedicated enrichment tool?

RapidAPI Hub lets you mix and match providers, swap them as quality or pricing changes, and pay only for what you call. Most teams pair a LinkedIn profile API with a company lookup API and tune the brief from there.

Will this work on Calendly Free?

Yes for new booking notifications, which are the only Calendly trigger this workflow needs. Some advanced Calendly features require a paid plan, but receiving a webhook when an invitee books does not.