Calendly meeting prep briefs in Slack with Snov.io campaign context

When a prospect books on Calendly, get a Slack prep brief that pulls their Snov.io record, the campaign that touched them, what they actually replied, and three tailored talking points.

Agentic Task
CalendlySnov.ioSlack BotSalesMeeting WorkflowsLead EnrichmentNotifications & Alerts
PromptCreate

Build an agent workflow that produces a sales meeting prep brief in Slack every time a new prospect books a meeting on Calendly.

Trigger: a Calendly outgoing webhook on the invitee.created event. Use the webhook trigger type. The payload contains the invitee email, name, scheduled event time, the event type, and any intake question answers.

Step 1. Take the invitee email from the Calendly payload and call Snov.io Get Prospect by Email to check whether this person is already in one of our prospect lists.

Step 2. If the prospect is found, use the prospect record to gather job title, company, location, and any known phone or social fields. Then call Snov.io List Campaigns to enumerate every drip campaign in the account. For each campaign whose prospect list contains this person, call Snov.io Get Campaign Replies and filter for replies whose sender email matches the invitee. Keep the most recent reply and its full message body. If the prospect has not replied to anything, fall back to whichever campaign most recently sent to them.

Step 3. If Snov.io Get Prospect by Email returns no record, fall back to Snov.io Find Prospects by Domain using the company domain extracted from the invitee email. Pull a short list (5 to 10) of other people at the same company so the rep can see the broader buying committee. Do not call Find Emails by Name and Domain here; that operation requires a known first and last name and is not appropriate when we are trying to surface unknown contacts.

Step 4. Generate a meeting prep brief in Slack mrkdwn formatting with these sections: (a) Who they are: name, title, company, location, scheduled meeting time. (b) Where they came from: name of the Snov.io campaign that touched them, sent date, and whether they have opened or clicked. (c) What they said: a direct quote of the most recent reply body, trimmed to two or three sentences. (d) Three talking points the rep should lead with, written based on the content of that reply (objection raised, feature interest, timing signal, etc.). (e) Red flags: if the reply contains negative sentiment, a complaint, an unsubscribe ask, or any pricing pushback, surface it explicitly under a Red Flags heading. If there are no red flags, omit the section. If the invitee was not in Snov.io, replace sections (b) through (e) with a Net New Contact section listing the other people found at the same company domain via Find Prospects by Domain.

Step 5. Post the brief to a private Slack channel using Slack Bot Send a Message. The channel ID should be configurable; default to a channel called sales-prep. Make sure the bot has been invited to the channel before the workflow runs.

Operational notes for the workflow author: Snov.io credentials are an API User ID plus API Secret which the platform exchanges for a one-hour Bearer token automatically. List Campaigns, Get Campaign Replies, and Find Prospects by Domain are all free operations; Get Prospect by Email costs credits. Snov.io rate limit is roughly 60 requests per minute, so when iterating campaigns prefer the campaign analytics shortcut where possible and short-circuit as soon as a matching reply is found. Find Prospects by Domain is asynchronous: start the task, then poll the result endpoint until status is completed.

What does this prompt do?

  • Listens for new Calendly bookings and immediately pulls up everything Snov.io knows about the invitee.
  • Surfaces the exact outbound campaign that touched the prospect and the most recent reply they sent back, so reps see real engagement, not just a name.
  • Generates three talking points based on what the prospect actually said, plus a red flag warning for negative sentiment or past complaints.
  • Posts the whole brief to a private Slack channel five minutes before the call, with a fallback that surfaces other contacts at the same company when the invitee is brand new.

What do I need to use this?

  • A Calendly account that can send outgoing booking webhooks (paid Calendly plans).
  • A Snov.io account on a paid plan with API access and at least one drip campaign running.
  • A Slack workspace and a private channel where the brief should land.

How can I customize it?

  • Change the Slack channel, or have the brief sent as a direct message to the rep who owns the meeting instead.
  • Adjust the talking points format (bullets vs. short paragraph) or swap the red flag rules for your own sentiment criteria.
  • Turn the buying-committee fallback on or off, or tighten it to specific job titles like VP or Director.

FAQs

What happens if the person who booked is not in our Snov.io lists?
The brief still posts to Slack. It marks the invitee as a net-new contact, and the fallback uses their email domain to pull other people at the same company so the rep at least knows the broader buying committee.
Does this work with any Calendly event type?
Yes. The workflow triggers on any new booking across your account. You can narrow it to a specific event type (for example, only sales demos) if you don't want a brief for every meeting.
How fast does the brief arrive after someone books?
Within seconds of the Calendly booking. The brief is in Slack before the confirmation email lands in the prospect's inbox.
Will the brief include the actual reply text from our outbound campaign?
Yes. The agent reads the most recent reply the prospect sent to one of your Snov.io campaigns and quotes the relevant part directly in the brief so you can respond to what they actually said.
Can I send this to a private channel instead of a public one?
Yes. Add the Slack bot to the private channel once, and the brief will post there. Most teams use a private channel like #sales-prep or DM the rep on the meeting.

Related templates

Review desk for portal forms your team still fills in by hand

Stage a batch of filings overnight, then approve each completed form from a screenshot before anything is ever submitted.

Kernel
Google Sheets
Slack Bot
App
Client-by-client cold email pipeline review for agencies

Pick a client and a date range to see sent, replies, meetings booked and the real deal value your cold email produced, campaign by campaign.

Instantly
HubSpot
Slack Bot
App
Audit what Intercom's Fin AI actually resolved before you pay

Review every conversation Fin closed as resolved, judge which ones actually stuck, and see what the gap is worth against your bill.

Intercom
Google Sheets
Slack Bot
App
One triage console for every Jira service desk queue

Merge your IT, HR and Facilities queues into one list ranked by SLA time left, then reply, change status and escalate without ever opening Jira.

Jira Service Management
Jira
Slack Bot
App
Run your Webflow site translations from one review desk

See every page's translation status at a glance, edit translations side by side with the English, and publish only what your team has actually approved.

Webflow
JigsawStack
Slack Bot
+1
App
Legal contract intake desk your teams use instead of email

One place for sales and ops to request an NDA or vendor agreement, watch its status, and let legal launch the contract in a single click.

Ironclad
Slack Bot
General Input Database
App

Stop walking into demos cold.

Connect Calendly, Snov.io, and Slack once, and Geni hands your reps a campaign-aware prep brief the moment a meeting is booked.