Instant Slack pre-call briefs the moment a Calendly meeting is booked

When a prospect books on Calendly, post a one-screen Slack brief with company logo, industry, location, socials, their booking answers, and talking points.

Agentic Task
CalendlyContext.devSlack BotSalesOperationsLead EnrichmentMeeting WorkflowsNotifications & Alerts
PromptCreate

Whenever a prospect books time on my Calendly link, I want an agent to push a one-screen pre-call brief into Slack so my reps walk into every demo prepared.

Trigger: a Calendly webhook on the invitee.created event. Fire as soon as a booking is confirmed.

Step 1. Read the booking. Pull the invitee's email, full name, the event type, the scheduled start time, and any answers to booking-form questions straight from the webhook payload. If any of those fields are missing, fall back to Calendly's Get Event Invitee using the invitee URI on the payload.

Step 2. Enrich the company. Call Context.dev's Retrieve Brand Data by Email with the invitee's email to resolve the company brand record: logo, one-line description, NAICS industry, headquarters location, and social links. Context.dev rejects free and disposable email providers (Gmail, Yahoo, Outlook, etc.) with a 422 — when that happens, skip enrichment gracefully and continue. If the brand record comes back without an industry, optionally call Context.dev's Classify NAICS Industries on the domain to fill it in.

Step 3. Post the brief. Use Slack Bot's Send a Message to post a compact briefing card into the channel #sales-briefs (or DM the meeting host, depending on the event type). The message should include: company name and logo, the one-line description, industry and location, social links, the prospect's name, their answers to the booking-form questions, and two or three talking points drafted from the company's brand description and what they wrote on the form.

Fallback behavior: if the brand lookup is skipped (free email) or returns no match, still post the message with the raw Calendly details (name, email, event type, time, booking answers) and a clear "no brand match" note at the top so nothing silently drops.

Keep the Slack message short enough to read at a glance and use Slack's mrkdwn formatting so the brand name and section headers stand out.

What does this prompt do?

  • Fires the instant someone books time on your Calendly link, so reps see the brief before they accept the calendar invite.
  • Looks up the prospect's company by their work email and pulls logo, one-line description, industry, location, and social links.
  • Posts a compact briefing card to your sales Slack channel (or DMs the meeting host) with the prospect's name, their booking-form answers, and two or three talking points drafted from the company's brand description.
  • Still posts the raw Calendly details with a clear no brand match note when the email is a personal address, so a booking never silently drops.

What do I need to use this?

  • A Calendly account with permission to install webhooks on your scheduling link.
  • A Context.dev account for the brand lookup (free and personal email addresses are skipped by design).
  • A Slack workspace and the channel or person you want the brief posted to.

How can I customize it?

  • Change where the brief lands: a shared sales channel, the meeting host's DM, or a per-rep channel.
  • Tweak which fields show up on the card (drop the socials, add the event type, hide the industry, etc.).
  • Adjust the talking-point voice so it matches how your team actually opens a discovery call.

FAQs

What happens if the prospect books with a Gmail or Yahoo address?
The brief still gets posted with their name, the event type, and any booking-form answers, plus a clear note that brand data could not be matched. Nothing silently drops.
How fast does the brief arrive in Slack?
Within a few seconds of the booking. Calendly fires the event the moment the meeting is confirmed, so the brief is usually waiting before the calendar invite even hits inboxes.
Can it DM the specific rep who owns the meeting instead of posting in a channel?
Yes. You can route the brief to the meeting host's Slack DM, a shared channel, or a per-rep channel based on the event type.
Will this work for every Calendly event type, or only one?
Either. You can scope it to a single demo link or run it across every event type on your account, and use the event type to decide where the brief goes.
Do I have to set up the Calendly webhook by hand?
No. When you connect Calendly, the webhook for new bookings is registered for you behind the scenes.

Related templates

Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

1Password
Rippling
Slack Bot
+1
Agentic Task
Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Amazon S3
Slack Bot
Google Sheets
Agentic Task
Log Agorapulse social conversations to HubSpot contacts

Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.

Agorapulse
HubSpot
Slack Bot
Agentic Task
Clean up HubSpot contacts from your Amazon SES suppression list

Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.

Amazon SES
HubSpot
Slack Bot
Agentic Task
Draft polite follow-ups for emails that never got a reply

Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.

Aurinko
Google Sheets
Slack Bot
Agentic Task
Replay failed SQS messages when a bug fix is merged

When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.

Amazon SQS
GitHub
Slack Bot
Agentic Task

Stop walking into demos cold.

Connect Calendly, Context.dev, and Slack once, and every new booking turns into a one-screen pre-call brief for your reps.