Calendly to Slack, never miss a new booking
A new Calendly booking comes in, and you find out late. The Slack channel is quiet, your inbox is noisy, and the meeting is suddenly “in 10 minutes” with no context.
This hits sales reps hardest because speed matters, but client-facing consultants and marketing leads routing inbound calls feel it too. With Calendly Slack alerts, you stop relying on chance and start getting a clean notification the moment someone books.
This workflow listens for new bookings, extracts the details people actually need, and sends an AI-written Slack message plus a polished Outlook email. You’ll see what it automates, what it changes day-to-day, and what you need to run it.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Calendly to Slack, never miss a new booking
flowchart LR
subgraph sg0["Calendly Event Flow"]
direction LR
n0@{ icon: "mdi:swap-vertical", form: "rounded", label: "Edit Fields", pos: "b", h: 48 }
n1@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
n2@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
n3@{ icon: "mdi:cog", form: "rounded", label: "Send a message", pos: "b", h: 48 }
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/calendly.svg' width='40' height='40' /></div><br/>Calendly Event"]
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Slack Message"]
n6@{ icon: "mdi:robot", form: "rounded", label: "Email Generator", pos: "b", h: 48 }
n0 --> n6
n4 --> n0
n6 --> n3
n6 --> n5
n1 -.-> n6
n2 -.-> n6
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n4 trigger
class n2,n6 ai
class n1 aiModel
classDef customIcon fill:none,stroke:none
class n4,n5 customIcon
The Problem: New bookings get missed (or noticed too late)
Calendly is great at letting people book time. It’s not great at making sure the right humans react in time. If you’re checking your calendar a few times a day, or scanning email between calls, you’re already behind. The result is small but painful: you show up unprepared, you ask questions the form already answered, and you waste the first five minutes re-orienting. Multiply that by a week of bookings and it turns into a steady drip of lost momentum.
It adds up fast. Here’s where it breaks down in the real world.
- You spot the booking after the fact because the notification blended into every other email.
- Slack updates happen inconsistently, so teammates assume “someone else saw it.”
- Key context lives in form answers, but nobody has time to open Calendly and hunt for it.
- When bookings are forwarded manually, names, times, and meeting reasons get paraphrased (and details get lost).
The Solution: Instant Slack + Outlook notifications for every Calendly booking
This n8n workflow listens for the invitee.created event in Calendly, which means it fires the second a meeting is booked. From there, it pulls out the details you care about (invitee name, email, start time, and the “reason for meeting” form answers). Then an AI agent turns those raw fields into two finished messages: a Slack alert that’s easy to scan in a busy channel, and an HTML email sent through Microsoft Outlook that you can keep for your own prep. Finally, both messages get delivered automatically so the booking becomes visible to you (and your team) without anyone copying and pasting.
The workflow starts with a Calendly trigger and a quick “map the payload” step so fields are consistent. The AI agent then writes the notification copy using an OpenAI chat model and a structured output mapper, and sends it out to Outlook and Slack in one pass.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you get 4 Calendly bookings a day. Manually, you might spend about 10 minutes per booking checking Calendly, copying form answers into Slack, and forwarding details to your inbox, which is roughly 40 minutes daily. With this workflow, the “work” is basically zero: the trigger fires instantly, the AI message is generated in about a minute, and Slack + Outlook are updated automatically. That’s around half an hour back every day, and the notifications are more consistent than anything you would write in a rush.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Calendly to detect new meeting bookings
- Slack to post alerts to a channel
- OpenAI API key (get it from the OpenAI dashboard)
Skill level: Beginner. You’ll connect accounts, paste an API key, and pick where notifications should go.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Calendly booking triggers the workflow. When a new invitee books (invitee.created), n8n receives the event immediately, so you’re not waiting on email delays or calendar refreshes.
Booking fields get cleaned up. The workflow maps the payload into predictable fields (name, email, start time, reason). That small step matters because it keeps your messages consistent even when Calendly question formats change.
AI generates the notification copy. An AI agent powered by an OpenAI chat model writes two outputs: a short Slack alert for fast scanning, plus a more detailed HTML email that reads like something you’d send yourself on purpose.
Slack and Outlook get updated. The workflow posts to your chosen Slack channel and sends the email via Microsoft Outlook, so you can prep from either place depending on how your day runs.
You can easily modify the Slack message format to match your team’s style, or change the email template to include extra fields like location or event type. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Calendly Trigger
Set up the workflow to start when a new Calendly invitee is created.
- Add the Calendly Booking Trigger node as the trigger.
- Set Events to
invitee.created. - Credential Required: Connect your calendlyApi credentials.
Step 2: Connect Calendly Payload Fields
Map the key booking fields so they can be used in the AI prompt and notifications.
- Add the Map Payload Fields node after Calendly Booking Trigger.
- In Map Payload Fields → Assignments, set payload.email to
{{ $json.payload.email }}. - Set payload.questions_and_answers[0].answer to
{{ $json.payload.questions_and_answers[0].answer }}. - Set payload.name to
{{ $json.payload.name }}. - Set payload.scheduled_event.start_time to
{{ $json.payload.scheduled_event.start_time }}.
Step 3: Set Up the AI Notification Composer
Configure the AI to generate both an HTML email and a Slack message in a structured format.
- Add the Compose Notification Text node after Map Payload Fields.
- Set Text to
=Name: {{ $json.payload.name }} About: {{ $json.payload.questions_and_answers[0].answer }} Start Time: {{ $json.payload.scheduled_event.start_time }}. - Enable Prompt Type =
defineand ensure Has Output Parser is enabled. - Attach OpenAI Chat Engine as the language model for Compose Notification Text.
- Credential Required: Connect your openAiApi credentials in OpenAI Chat Engine.
- Attach Structured Output Mapper as the output parser for Compose Notification Text and keep the JSON schema example as
{ "email": "html email", "slack": "Slack Message" }.
Step 4: Configure Notification Outputs
Send the AI-generated content via Outlook email and Slack in parallel.
- Connect Compose Notification Text to both Dispatch Outlook Email and Post Slack Alert in parallel.
- In Dispatch Outlook Email, set Subject to
Calendly Details. - Set Body Content to
{{ $json.output.email }}and Body Content Type tohtml. - Set To Recipients to
{{ $('Map Payload Fields').item.json.payload.email }}. - Credential Required: Connect your microsoftOutlookOAuth2Api credentials.
- In Post Slack Alert, set Text to
{{ $('Compose Notification Text').item.json.output.slack }}. - Select the Channel and set Authentication to
oAuth2. - Credential Required: Connect your slackOAuth2Api credentials.
Step 5: Test and Activate Your Workflow
Validate the end-to-end flow and enable it for live bookings.
- Click Test workflow in n8n and create a test booking in Calendly.
- Confirm Dispatch Outlook Email sends an HTML email and Post Slack Alert posts the Slack message.
- Verify that the output JSON from Compose Notification Text contains both
emailandslackkeys. - When satisfied, toggle the workflow to Active to run automatically.
Common Gotchas
- Calendly credentials can expire or the token may not include the right scopes. If things break, check n8n → Credentials → your Calendly credential first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Slack OAuth access sometimes loses channel permissions after workspace changes. If messages stop posting, confirm the app is still allowed in the target channel and reselect the channel in the Slack node.
Frequently Asked Questions
About 30 minutes if your accounts are ready.
No. You’ll connect Calendly, Slack, and Outlook, then paste your OpenAI API key.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs, which are usually a few cents per booking for short messages.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. Update the mapping step (“Map Payload Fields”) to include any extra Calendly fields you care about, then adjust the AI agent instructions so the Slack output matches your channel style (short, skimmable, and consistent). If you prefer a fixed template, you can also reduce AI creativity by tightening the prompt and relying on the structured output mapper to enforce the format. Common tweaks include adding the meeting link, tagging an owner in Slack, and changing the Outlook subject line.
Usually it’s permissions. Reconnect Slack in n8n, then confirm the app is allowed to post in the destination channel and that the channel selected in the Slack node still exists.
It depends on where you run it. On n8n Cloud, the limit is tied to your monthly executions, and each booking typically counts as one run. If you self-host, there’s no execution cap, so the practical limit becomes your server resources and API rate limits. For most small teams, handling dozens of bookings per day is completely normal.
Often, yes, if you care about formatting and control. n8n makes it easier to map fields cleanly, generate structured AI output, and send both Slack and Outlook messages without paying extra for branching and multi-step logic. Zapier and Make can absolutely do this too, but the moment you want “Slack message + HTML email + consistent formatting + a fallback path,” you’re usually building a more expensive scenario. If you only need a basic two-line Slack ping, those tools are quick. Talk to an automation expert if you want help picking the simplest option for your setup.
Once this is live, every new booking lands with context in Slack and Outlook, automatically. You show up ready, and your team stops guessing.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
