cotera

Calendly Follow-Up Automator

Never forget to follow up after a meeting again. Automatically draft personalized follow-ups from your Calendly data and post them to Slack.

Post-meeting follow-upsCustomer successSlack notificationsAction items

The Challenge

After a full day of back-to-back Calendly meetings, the last thing you want to do is write individual follow-up emails for each one. Most follow-ups get delayed by a day or two, and some never happen at all. The meeting happened, but the momentum dies because nobody sent the recap.

What This Prompt Does

Review Yesterday

Pulls all meetings from yesterday's Calendly schedule

Get Meeting Context

Fetches event details, notes, and invitee responses

Draft Follow-Ups

Writes personalized messages based on meeting type

Post to Slack

Sends a summary with all drafts to your team channel

The Prompt

The Prompt

Task

Review my Calendly meetings from yesterday, pull the invitee details for each one, and draft personalized follow-up messages. Post a summary to Slack with the follow-ups ready to send.

Input

The user provides a time range (default: yesterday) and optionally a Slack channel for the summary.

Context

Data to Pull

  1. Use @Calendly/Get Current UserName it "Calendly/Get Current User" and call it with @Calendly/Get Current User to get the user URI
  2. Use @Calendly/List EventsName it "Calendly/List Events" and call it with @Calendly/List Events for yesterday, status "active"
  3. For each event, use @Calendly/Get EventName it "Calendly/Get Event" and call it with @Calendly/Get Event to get full details including meeting notes
  4. For each event, use @Calendly/List Event InviteesName it "Calendly/List Event Invitees" and call it with @Calendly/List Event Invitees to get attendee info and booking form answers

What to Include in Follow-Ups

  • Reference the meeting topic and any specific discussion points from meeting notes
  • Include any booking form answers the invitee provided
  • Suggest a next step based on the event type (demo call = proposal, intro call = deeper dive, etc.)
  • Keep the tone professional but warm
  • Include a scheduling link for the next meeting if relevant

Follow-Up Rules

  • If the event was a "demo" or "discovery" type: suggest sending a proposal or scheduling a deeper dive
  • If the event was an "intro" or "get to know" type: suggest a follow-up meeting with more stakeholders
  • If the event was a "check-in" type: summarize action items and suggest a timeline
  • If meeting notes are available, reference specific things discussed

Output

For each meeting from yesterday:

Meeting: Event name, time, attendees

Follow-Up Draft: A ready-to-send email or message (2-3 paragraphs) that references the meeting, thanks the attendee, and proposes a clear next step.

Next Steps: Suggested action items.

If a Slack channel was provided, post the summary with all follow-up drafts to that channel using @Slack/Send MessageName it "Slack/Send Message" and call it with @Slack/Send Message.

Example Usage

Try asking:

  • →"Draft follow-ups for all of yesterday's Calendly meetings"
  • →"What meetings did I have yesterday? Write follow-up emails for each."
  • →"Review my Calendly meetings from Monday and create follow-up drafts, post to #sales"