Calendly booking → HubSpot meeting + Google Docs prep sheet + Slack alert
Booked calls land in HubSpot with a prep sheet and a Slack alert within a minute.
A confirmed Calendly booking becomes a HubSpot contact and a logged meeting within a minute. The host gets a one-page prep sheet in Google Docs and a Slack message carrying the links. Built for sales, fundraising and recruiting teams that book calls through Calendly and lose the invitee's answers somewhere between the form and the call.
How it works
- Ca
Trigger
Invitee created: a booking is confirmed on a watched event type (Calendly's invitee.created webhook)
Calendly
- H
Step 1
Find or create the contact
Searches HubSpot by the invitee's email; creates the contact with name, email and any phone answer from the form, or updates the existing record and keeps its history.
- H
Step 2
Assign an owner
Matches the Calendly host's email to a HubSpot user and sets them as contact owner when the record has none, so round-robin bookings go to the person who took them.
- H
Step 3
Log the meeting
Logs a HubSpot meeting on the contact: the event type as title, start and end time from the booking, every form question and answer in the body, and the Calendly event link in the meeting's external URL field.
- if
Step 4
Assemble the prep sheet
Combines the booking details, the invitee's answers, and three fields from the contact record: lifecycle stage, number of associated deals, and last activity date.
- GD
Step 5
Create the prep sheet
Creates a new document in your chosen Drive folder, named after the invitee and the date, and inserts the assembled prep text under fixed headings.
- S
Step 6
Alert the host
Sends a direct message to the host, or a channel post, with the invitee's name, the start time in the timezone you set in the workflow, and links to the doc, the contact and Calendly's reschedule page.
What changes once it runs
- A HubSpot contact exists, or is updated, within a minute of every Calendly confirmation.
- Each booking is logged as a HubSpot meeting with the invitee's form answers in the body.
- The host holds a Google Doc prep sheet and a Slack message with three links before the call starts.
- Ownerless contacts are assigned to the Calendly host whose email matches a HubSpot user.
- Cancellations mark the HubSpot meeting as cancelled and post to the same Slack channel, through a second included workflow.
What you get
- n8n workflow export for invitee.created, tested against a live Calendly event type
- A second, smaller workflow for invitee.canceled that finds the meeting by its Calendly link, marks it cancelled and posts to Slack
- Make blueprint of the main flow
- Setup guide covering the Calendly webhook, the HubSpot private app scopes and the Slack bot
- Field-mapping sheet: each Calendly question against a HubSpot property, editable before import
- Recorded walkthrough of one booking flowing end to end
Before you start
- Calendly Standard, Teams or Enterprise; webhook subscriptions are not offered on the free plan
- HubSpot with a private app token that can read and write contacts, meetings and owners (the free CRM is enough)
- Google account with Docs and Drive access, and a folder for the prep sheets
- Slack workspace where you can install a bot user
- An n8n instance on a public URL so Calendly can deliver webhooks (n8n Cloud, or self-hosted behind a domain)
Built for
Questions before you buy
- Can I map the Calendly form questions to my own HubSpot properties?
- The field-mapping sheet lists each Calendly question label beside a HubSpot property; change the right-hand column and re-import. Custom properties have to exist in HubSpot first, and the guide shows where to create them.
- What happens if HubSpot rejects the write or the token has expired?
- Each of the three HubSpot steps retries, with a pause between attempts. If they still fail, the run stops with the error logged in n8n, and the Slack message goes out anyway with a line saying the CRM write did not complete. No booking is dropped without a trace.
- Does it work with round-robin and collective event types?
- Yes. Calendly's payload names the host who was assigned, and the workflow uses that person for the contact owner and the Slack DM. Subscribe the webhook at organisation level to cover every member; a user-level webhook covers one account only.
- Do I need a paid n8n plan?
- No. The free self-hosted Community edition runs it, and so does the cheapest n8n Cloud plan. The one hard requirement is a URL Calendly can reach. A laptop behind a home router will not receive webhooks.
- Can it run on Make or Zapier?
- Make, yes: a blueprint using the Calendly, HubSpot, Google Docs and Slack modules is in the package. Zapier can build the same flow as a multi-step Zap on a paid plan, but we do not ship a Zapier version of this one.
Nearby on the shelf
Whole catalog- ZAIHSMade to order
Zoom transcript → AI call summary on the HubSpot contact + Slack post
Zoom call summaries reach the HubSpot contact minutes after the transcript is ready.
Scheduling & meetings$199 - CaSFSMade to order
Calendly booking → Salesforce status update, logged task + Slack alert
Booked meetings land on the Salesforce record within a minute, with a task and an alert.
Sales & CRM hygiene$99 - GCTwMade to order
Google Calendar appointment → day-before SMS reminder via Twilio
Tomorrow's appointments get a text reminder from your Google Calendar each morning.
Scheduling & meetings$49
