Calendly to Outlook, polished follow ups sent fast
New meetings come in… and then the follow-up sits there. You meant to send it “right after,” but you got pulled into Slack, a client call, or a dozen tiny tasks.
This Calendly Outlook followup automation hits sales reps and founders first, but marketing leads and client-facing ops folks feel it too. The goal is simple: every new booking gets a polished email fast, without you drafting the same message again.
Below you’ll see exactly what the workflow does, the results you can expect, and what to watch out for when you turn it on.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Calendly to Outlook, polished follow ups sent fast
flowchart LR
subgraph sg0["Calendly Event Flow"]
direction LR
n0@{ icon: "mdi:swap-vertical", form: "rounded", label: "Edit Fields1", pos: "b", h: 48 }
n1@{ icon: "mdi:robot", form: "rounded", label: "AI Agent1", pos: "b", h: 48 }
n2@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model1", pos: "b", h: 48 }
n3@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser1", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Send a message2", pos: "b", h: 48 }
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/calendly.svg' width='40' height='40' /></div><br/>Calendly Event"]
n1 --> n4
n0 --> n1
n5 --> n0
n2 -.-> n1
n3 -.-> n1
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 n5 trigger
class n1,n3 ai
class n2 aiModel
classDef customIcon fill:none,stroke:none
class n5 customIcon
The Problem: Great bookings go cold without a fast follow-up
Calendly makes booking easy. The messy part is what happens in the five minutes after someone schedules. If the confirmation email is generic, people show up unsure what you do or what they should prepare. If you send a manual follow-up, you either copy-paste an old template (and forget to change the name or time) or you try to “make it personal” and burn mental energy on a message you’ve written a hundred times. Then there’s timing. A follow-up sent two hours later feels like an afterthought, even if the meeting is still days away.
The friction compounds. Here’s where it breaks down.
- You waste about 10 minutes per booking writing a “quick note” that is never actually quick.
- Details get missed, like the meeting date, the prospect’s reason for booking, or what happens next.
- Teams end up with inconsistent voice and formatting, which makes your brand look scattered.
- When bookings scale, the follow-up becomes the bottleneck and response times quietly slip.
The Solution: AI-written Outlook follow-ups triggered by Calendly
This workflow listens for a new Calendly booking (the invitee.created event). The moment someone schedules, n8n grabs the invitee’s key details like name, email, the reason they entered for the meeting, and the scheduled time. Then an AI agent uses that context to write a helpful, human-sounding HTML email that feels personal without getting weird. It also includes practical details (like the meeting date) and a placeholder phone number (111-111-1111) so your message looks complete and professional. Finally, n8n sends the finished email through Microsoft Outlook, so it lands like it came from your real business inbox.
The workflow starts with a Calendly trigger. It maps invite details into a clean structure, hands that to OpenAI to compose the email, and then dispatches the HTML message via Outlook. No tab switching. No drafting.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you get 15 new Calendly bookings in a week. If each follow-up takes about 10 minutes to write, that’s roughly 2.5 hours of repetitive work, plus the extra time hunting for the meeting date and copying the right template. With this workflow, you do almost none of that: the booking triggers instantly, the AI drafts the email in a minute or two, and Outlook sends it. Realistically, you’re down to a quick spot-check, which is more like 2 minutes per booking.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Calendly to trigger on new bookings
- Microsoft Outlook to send the follow-up email
- OpenAI API key (get it from the OpenAI API dashboard)
Skill level: Beginner. You’ll connect accounts, paste an API key, and edit a prompt if you want a specific tone.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Calendly booking comes in. The workflow listens for the invitee.created event, so it only runs when someone actually schedules.
The invitee details get cleaned up. n8n maps the name, email address, meeting date/time, and the “reason for meeting” into consistent fields you can reuse in the email.
AI writes the follow-up email. An AI agent (powered by the OpenAI chat model) creates an HTML-formatted message that references the person’s request, confirms the scheduled time, and includes your contact line (the workflow uses 111-111-1111 as a placeholder).
Outlook sends it automatically. The final HTML is passed into Microsoft Outlook so the message comes from your real mailbox, with the formatting intact.
You can easily modify the email tone to match your brand voice based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Calendly Trigger
This workflow starts when Calendly confirms a new invitee. Configure the trigger to listen for new invitee events.
- Add the Calendly Invite Trigger node as the workflow trigger.
- Set Events to
invitee.created. - Credential Required: Connect your calendlyApi credentials.
Step 2: Connect OpenAI for Email Generation
The AI step uses OpenAI to generate the follow-up email content.
- Add the OpenAI Chat Engine node and set the Model to
gpt-4.1-mini. - Credential Required: Connect your openAiApi credentials.
- Ensure OpenAI Chat Engine is connected as the language model for Compose Email Agent.
- Attach Structured Response Parser to Compose Email Agent as the output parser; no credentials are needed for the parser itself.
Step 3: Set Up Invite Mapping and AI Prompting
Map invite details into a clean structure, then pass those details into the AI agent for email drafting.
- Add the Map Invite Details node and configure the assignments:
- payload.email →
={{ $json.payload.email }} - payload.questions_and_answers[0].answer →
={{ $json.payload.questions_and_answers[0].answer }} - payload.name →
={{ $json.payload.name }} - payload.scheduled_event.start_time →
={{ $json.payload.scheduled_event.start_time }}
- payload.email →
- Add the Compose Email Agent node and set Text to
=Name: {{ $json.payload.name }} About: {{ $json.payload.questions_and_answers[0].answer }} Start Time: {{ $json.payload.scheduled_event.start_time }}. - Set Prompt Type to
defineand enable Has Output Parser. - In System Message, use:
You are a helpful assistant. Write an email to the user. Elaborate on how we can help them with their topic and give my fake phone number for now 111-111-1111. Write the email in html. also put the meeting date in there. output like this. { "email": "html email" }
email field. If the system message doesn’t enforce this, Dispatch Outlook Email will not receive valid HTML.Step 4: Configure the Email Delivery
Send the AI-generated HTML email using Outlook.
- Add the Dispatch Outlook Email node.
- Set Subject to
Calendly Details. - Set Body Content to
={{ $json.output.email }}. - Set To Recipients to
={{ $('Map Invite Details').item.json.payload.email }}. - Set Body Content Type to
html. - Credential Required: Connect your microsoftOutlookOAuth2Api credentials.
Step 5: Test and Activate Your Workflow
Validate the end-to-end flow from Calendly to Outlook and then activate the workflow.
- Click Execute Workflow and trigger a test Calendly invitee event.
- Confirm the execution flow: Calendly Invite Trigger → Map Invite Details → Compose Email Agent → Dispatch Outlook Email.
- Verify the Outlook message arrives with HTML formatting and the correct recipient email.
- Once verified, toggle Active to enable the workflow in production.
Common Gotchas
- Calendly credentials can expire or need specific permissions. If things break, check the n8n Credentials entry for Calendly and confirm your personal access token is still valid.
- Microsoft Outlook OAuth can quietly disconnect when a password changes or an admin policy updates. If emails stop sending, re-authenticate the Outlook credential and confirm the “Send a message” node is using the right mailbox.
- Default AI prompts are generic. Add your brand voice and a few “do/don’t” rules early, or you will keep rewriting the email after it’s sent (which defeats the point).
Frequently Asked Questions
About 30 minutes if your Calendly, Outlook, and OpenAI accounts are ready.
No. You’ll connect credentials and paste an API key. The main “editing” is tweaking the AI prompt so it sounds like you.
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 usage, which is usually a few cents per email for light-to-moderate volumes.
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 it’s one of the best reasons to use n8n here. You can adjust the AI Agent instructions to create different tones for sales calls vs. onboarding vs. support. If you have multiple Calendly event types, you can also branch the workflow so one booking type gets a shorter email and another includes prep questions. The mapped fields (name, question, start time) stay the same, which keeps it simple.
Most of the time it’s OAuth re-authentication. Reconnect the Microsoft Outlook credential in n8n and confirm the “Send a message” node still points to it. If you’re in a managed Microsoft 365 environment, an admin policy can also block sending via API until the app is approved.
A lot.
Often, yes, especially if you care about message quality and control. n8n handles the AI agent flow, structured parsing, and HTML formatting without forcing you into expensive “premium” steps, and self-hosting removes execution limits altogether. It’s also easier to add guardrails, like branching by meeting type, or logging every email you sent. Zapier or Make can be quicker for a basic “send template email” setup, but this workflow is really about personalized content. If you’re on the fence, Talk to an automation expert and you’ll get a straight answer.
Set it up once, and every new booking gets a fast, polished follow-up without you lifting a finger. Honestly, it’s the easiest way to look more responsive overnight.
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.