Connect Cal.com Bookings to Twenty CRM With Webhooks and n8n
Step by step: subscribe a Cal.com webhook, verify its signature in n8n, and upsert the booker as a person and an opportunity in Twenty CRM. Covers reschedules, cancellations, duplicates, and the URL rules that break most first attempts.

A booking in Cal.com is worth nothing to your sales team until it exists in your CRM. The fix is a short, durable pipeline: Cal.com fires a webhook on every booking event, n8n verifies and reshapes the payload, and Twenty CRM receives an upsert through its REST API. No CSV exports, no Zapier task meter, no rep retyping email addresses at 6pm.
This guide builds that pipeline end to end: the real Cal.com payload structure, HMAC signature verification, field mapping into Twenty's schema-generated API, and the dedup and reschedule logic that most tutorials skip. The user-scoped parts work on hosted Cal.com, Cal.com Enterprise self-hosted, and Cal.diy, the open-source community edition; team scopes and routing forms need hosted Cal.com or Enterprise. Twenty Cloud and self-hosted Twenty both work.
What you need and how the pieces fit
Prerequisites
- Cal.com, cloud or self-hosted, with access to Settings, Developer, Webhooks. Mind the licensing change: Cal.com itself moved to closed source in April 2026, and the open-source codebase continues as Cal.diy, an MIT-licensed community edition recommended for personal, non-production use, per Cal.com's announcement. Cal.diy keeps user-level webhooks but drops teams, routing forms, and workflows. The user-scoped parts of this guide work on Cal.diy; team-scoped webhooks and routing forms need hosted Cal.com or a Cal.com Enterprise self-hosted license.
- Twenty CRM, cloud or self-hosted, with admin rights to create an API key. REST API, GraphQL API, and webhooks are available on every plan including the free self-hosted option, per the Twenty pricing page.
- n8n, any recent version, reachable over a public HTTPS URL. This last point matters: Cal.com's hosted service refuses webhook subscriber URLs that use plain HTTP, private IPs, or localhost, per the Cal.com webhooks documentation. Self-hosted Cal.com can post to private addresses, but hosted Cal.com cannot. If your n8n sits behind a VPN, put a public reverse proxy in front of just the webhook path.
- About an hour.
If you would rather not host the pieces yourself, we deploy and run both Twenty and Cal.com for clients as part of our managed open-source stack service.
The architecture
The pattern is webhooks out, API in. Cal.com pushes an event to n8n the moment something happens. n8n checks the signature, normalizes the payload, and calls Twenty's REST API. Twenty never polls Cal.com; Cal.com never knows Twenty exists. We covered this pattern generically in How to Connect a Self-Hosted Stack With n8n and Webhooks; this post is the deep, Cal.com-specific version with real payloads.
One alternative worth knowing: n8n ships a dedicated Cal Trigger node, but it only supports four events (booking cancelled, created, rescheduled, meeting ended) and requires Cal.com API credentials. The generic Webhook node receives every event Cal.com emits, including routing-form submissions, so this guide uses that.
Step 1: Create the Twenty API key and check your schema
Twenty has no static API reference. Each workspace generates REST and GraphQL endpoints from its own schema, so a custom object you invent gets the same endpoints as the built-in Person or Company, per the Twenty API documentation.
- In Twenty, go to Settings, Developers, API, and click Create key. Copy it immediately; Twenty shows it once.
- Note your base URL. Cloud is
https://api.twenty.com/, self-hosted ishttps://your-domain/. - Open the interactive playground under Settings, Developers, API. It shows the exact request bodies your schema expects. Use it, because composite fields like
nameandemailson a Person have a nested shape your workspace documents for you.
Plan for three objects: Person (the booker), Opportunity (the deal the booking represents), and optionally Note (meeting details attached to the person). Add one custom text field to Opportunity, for example bookingUid, so you can deduplicate on Cal.com's booking identifier later. Both REST and GraphQL support batches of up to 60 records per request, and GraphQL adds batch upsert, which is useful when you outgrow the one-at-a-time version below. The API rate limit is 100 requests per minute per workspace, far above anything this pipeline produces.
Step 2: Create the n8n webhook endpoint
In n8n, create a workflow starting with a Webhook node. Set the method to POST and the path to something like calcom-bookings.
Two details from the n8n Webhook node documentation trip people up:
- The node exposes a test URL and a production URL. The test URL only receives requests while you are actively listening in the editor. The production URL only works once the workflow is activated. Configure Cal.com with the production URL before you flip the workflow on.
- The default maximum request body is 16MB, far above any booking payload, but remember it if you later reuse the endpoint for file uploads.
Add Header Auth with a long random token as a first gate. Cal.com lets you attach up to 10 custom headers to a webhook subscription, so the webhook can carry an Authorization: Bearer header that n8n checks before doing any work. This is defense in depth, not a substitute for the signature check in the next step.
Step 3: Subscribe Cal.com and verify the signature
In Cal.com, go to Settings, Developer, Webhooks and create a subscription. Four choices matter:
- Scope. Webhooks exist at user, individual event type, team, and organization level. If bookings land on team event types, a user-scoped webhook never fires. For a sales team, subscribe at team level. Team- and organization-level scopes exist only on hosted Cal.com and Enterprise self-hosted; Cal.diy is limited to user-level webhooks.
- Events. Subscribe to
BOOKING_CREATED,BOOKING_RESCHEDULED, andBOOKING_CANCELLED. AddFORM_SUBMITTEDif you use routing forms (hosted Cal.com only; Cal.diy has no routing forms); that event has a different payload shape, covered in step 5. If you are still deciding how bookings should be distributed across the team, our Cal.com routing forms and round robin guide covers the scheduling side. - Subscriber URL. Paste the n8n production URL.
- Secret. Set one. Cal.com then sends an
x-cal-signature-256header with every delivery, an HMAC-SHA256 of the raw request body keyed with your secret, per the Cal.com webhook payload reference.
Verify the signature before touching the payload. In a Code node immediately after the Webhook node:
const crypto = require('crypto');
const secret = 'your-webhook-secret';
const sent = $json.headers['x-cal-signature-256'];
const expected = crypto
.createHmac('sha256', secret)
.update($json.rawBody)
.digest('hex');
if (sent !== expected) {
throw new Error('Invalid Cal.com signature');
}
return [$json];
The hash must run over the raw body bytes, not a re-serialized JSON object; enable the raw body option on the Webhook node so the Code node hashes exactly what Cal.com signed. If your n8n sandbox disables require, the built-in Crypto node computes HMAC-SHA256 without code.
One more versioning detail: Cal.com sends an x-cal-webhook-version header (the reference shows versions like 2021-10-20 and 2026-07-27), and payload shapes differ between versions. Log the header on every delivery so a Cal.com upgrade never silently changes your mapping.
Step 4: Map the payload and upsert into Twenty
A BOOKING_CREATED delivery wraps everything in an envelope: triggerEvent, createdAt, and a payload object. The useful fields inside payload, from the Cal.com payload reference:
payload.attendees[0].emailandpayload.attendees[0].name(recent versions also carryfirstNameandlastName)payload.organizer.email, the team member who got the bookingpayload.startTimeandpayload.endTime, ISO timestampspayload.uid, the booking identifier you will use for deduppayload.metadata.videoCallUrlorpayload.locationpayload.responses, the answers to your booking questions, including notes and guests
The n8n flow after the signature check:
- Switch node on
triggerEvent. RouteBOOKING_CREATEDto the create path; send reschedules and cancellations to step 5. - Find the person. HTTP Request node: GET to
/rest/peoplefiltered by the attendee email. The exact filter syntax for your workspace is in the Twenty API playground from step 1. - Create if missing. If the search returns nothing, POST to
/rest/peoplewith the name and email. If it returns a record, keep its ID and move on. This is your contact-level dedup. - Create the opportunity. POST to
/rest/opportunitieswith a name likeDemo with Jane Mwangi, the person relation, the meeting time in a custom field or note, andbookingUidset topayload.uid. Store the video link in a note on the record. - Optional: assign the owner. Match
payload.organizer.emailto a Twenty workspace member and set them as the opportunity owner, so the right rep sees the deal.
A worked example with real numbers
Take a six-person sales team running hosted Cal.com and self-hosted Twenty and n8n:
- Cal.com Teams plan: $12 per user per month billed yearly, so $72 per month for the team. Teams is the tier whose feature list includes routing forms, round robin scheduling, and custom APIs with webhooks, per the Cal.com pricing page.
- Twenty self-hosted: no license cost; the same API and webhooks ship in the free self-hosted option. On Twenty Cloud the Pro plan would be $9 per user per month, $54 for six.
- n8n Community Edition self-hosted: no license cost. n8n's cloud pricing is based on monthly workflow executions rather than per-step counting, per the n8n pricing page.
At 20 bookings a week the team handles about 87 bookings a month. With created, rescheduled, and cancelled events that is roughly 261 webhook deliveries, a trivial load for any n8n tier. The manual alternative is a rep spending about three minutes retyping each booking into the CRM: those same 261 touches are about 4.3 hours of copy-paste a month, plus the bookings that never get entered at all.
Step 5: Handle reschedules, cancellations, and duplicates
Bookings change. Design for it on day one.
- Reschedules. A
BOOKING_RESCHEDULEDevent carries the bookinguid. Because you stored that uid on the opportunity in step 4, the reschedule path is a search onbookingUidfollowed by an update of the meeting time, not a new record. If you ever move to bulk imports, Twenty's GraphQL API supports batch upsert operations likeCreateCompanies, which collapses the search-then-create pattern into one call. - Cancellations. On
BOOKING_CANCELLED, find the opportunity bybookingUidand move it to a closed-lost style stage, or add a cancellation note if your pipeline treats no-shows differently from lost deals. Deleting the record destroys history; update it instead. - Duplicate deliveries. Webhook systems can deliver the same event more than once. The
bookingUidcheck before any create makes a redelivery harmless. - Routing form submissions.
FORM_SUBMITTEDhas a different shape:payload.responsesis keyed by the question text rather than by fixed attendee fields, and there is no booking yet. Map it to a Person plus a task for follow-up, not to an opportunity. Cal.com also emitsFORM_SUBMITTED_NO_EVENTabout 15 minutes after a submission when the visitor never picked a slot, which is a useful abandoned-lead signal for the sales team.
Common mistakes
- Testing against the test URL. The n8n test URL only works while you click Listen in the editor. Everything looks fine in testing, then goes silent in production because Cal.com still points at the test URL. Always hand Cal.com the production URL and activate the workflow.
- Subscribing at the wrong scope. A user-scoped webhook never sees bookings made on team event types. Match the scope to where the event types live.
- Verifying the signature against re-serialized JSON. The HMAC covers the raw request body. Hash a re-stringified object and verification fails intermittently depending on key order.
- Assuming one payload shape forever. Payload versions change; check
x-cal-webhook-versionin your logs after every Cal.com upgrade. - Letting n8n sit behind a private address while using hosted Cal.com. Hosted Cal.com will not post to private IPs or plain HTTP. Either expose the webhook path publicly or self-host Cal.com.
- Treating Twenty's outbound webhooks as a way in. Twenty's own webhooks fire on record changes with
object.actionevent names likeperson.createdand no event filtering, per the Twenty webhooks documentation. They push data out of Twenty, for example to notify a Slack channel when the opportunity lands. They are a complement to this pipeline, not a replacement for the REST upsert into it.
When this is the wrong choice
- You want zero infrastructure. Cal.com documents a Zapier integration for exactly this case. You trade per-task pricing and less control for not running n8n at all.
- You only need a contact created, nothing more. Twenty's workflow builder includes a webhook trigger that can receive data directly, which we cover in Twenty CRM Workflow Automation: The Complete Guide. You lose n8n's error handling, branching, and multi-step logic, but for a single create-a-person step it can be enough.
- You need a marketing suite, not a CRM. Twenty is a CRM core: objects, pipelines, permissions, API. If you need email nurture sequences and landing pages in the same product, this stack will not replace HubSpot for you.
- You want to self-host the scheduler for a whole team. Since the April 2026 license change, the open-source edition (Cal.diy) has no teams, routing forms, or workflows; self-hosting those features means a Cal.com Enterprise license, which changes the cost math.
- Your scheduler is not Cal.com. The pattern transfers to any scheduler that emits signed webhooks, but the payload mapping in step 4 is Cal.com-specific.
Frequently asked questions
Does this work on the Cal.com free plan? User-level webhooks are configured under Settings, Developer, Webhooks and are not a paid extra. What the free plan lacks is the team layer this guide leans on: team event types, team-scoped webhooks, and routing forms sit on the Teams plan, whose feature list includes custom APIs per the pricing page. Cal.diy, the open-source community edition, has no plan gating but no team features either, so it fits a one-person booking page rather than a sales team.
Can I do this without n8n? Yes. Twenty workflows can trigger on an inbound webhook, and any small HTTP service can receive the POST and call the REST API. n8n earns its place when you need branching for reschedules and cancellations, retries, and a visual record of every execution.
What happens when someone reschedules or cancels? Cal.com fires BOOKING_RESCHEDULED or BOOKING_CANCELLED with the same booking uid you stored on the opportunity. Your n8n flow finds that record and updates the meeting time or stage instead of creating a duplicate.
How do I stop duplicate people in Twenty? Search /rest/people by the attendee email before every create, and only POST when the search is empty. For bulk work, Twenty's GraphQL API supports batch upserts of up to 60 records per request.
Is this setup GDPR friendly? If you self-host Cal.com, Twenty, and n8n, attendee data stays inside infrastructure you control, which simplifies data residency questions considerably. On the hosted path, review each vendor's data processing terms the way you would for any SaaS that touches personal data.
Where to go from here
If you want this running without maintaining the moving parts, our Business Automation service designs and operates n8n workflows like this one, and our managed stack work covers the Cal.com and Twenty deployments on either side of it. The workflow in this guide is a good first candidate: small, measurable, and easy to extend once it proves itself.
Related reading
About AI Agents Plus Editorial
AI automation expert and thought leader in business transformation through artificial intelligence.



