Every booking, a lead
The moment someone books a meeting, their lead is waiting in CRM for your team.
Calendly Integration
How to Connect
Calendly
Each booking becomes a CRM lead carrying the invitee details, routed to a pipeline and owner with duplicates merged. Someone books a meeting, and your sales team already has the lead.
- Every booking, a lead
- Pipeline & owner routing
- Duplicates merged
01Add a source
Add Calendly as a lead source
In the app, open Modules → Integrations → Lead Sources. Under Add a source, pick Calendly and click Add source. Each source gets its own webhook URL; every payload becomes a CRM lead.
- Its own webhook URL for every source
- Same screen for website forms, Jotform and Facebook
- Switch a source on or off at any time
Integrations
Lead sourcesConnect the places enquiries come from. Each source gets its own webhook URL.1 enabled
Calendly1 connected
Website Forms
Facebook Lead Ads
Jotform02Connect Calendly
One webhook URL for every booking
Open the source and copy its Webhook URL. In Calendly, create a webhook subscription with that URL for the invitee.created event. From then on, every new booking is posted to SpeedoOne with the invitee’s details.
- Copy the webhook URL in one click
- Calendly webhooks need a paid Calendly plan
- Rotate the token if the URL ever leaks
Calendly · calendly
Webhook URL
https://app.speedoone.com/…/calendly/4b7e…Copy
How to connect
- Copy the Webhook URL above.
- In Calendly, create a webhook subscription with this URL.
- Subscribe it to the
invitee.createdevent. - Book a test meeting — the invitee shows up in CRM as a lead.
Nov05
Lead createdDesign consultation · 30 minThu, 5 Nov · 11:00 – 11:30
Asha Mehtaasha@example.com+91 98765 43210
03Lead routing
Every lead reaches the right owner
Set a default product, default owner, pipeline and tags for the source. Leave the owner empty and your auto-assign rules pick one. The field map matches the invitee details to CRM fields.
- Default product when the booking has none
- Tags added to every lead
- Unmapped fields fall back to common names
Source settings
LabelCalendly — Consultations
Default productDesign consultation
Default ownerAnkit Jain
PipelineSales
Tags added to every lead
Field map — lead field ← path in the incoming payload (dot notation, e.g.
payload.email).
name←payload.name
email←payload.email
phone←payload.text_reminder_number
+ Add mapping
04Test & monitor
Test it before a real booking arrives
Paste a sample payload and click Parse — nothing is saved, you just see the leads it would create. Each source shows how many leads it has received, when the last one came in and the last error, if any.
- Parse a sample payload safely
- Received count and last received time
- Delete a source — leads already created stay
CalendlyEnabled
Received58
Last received1h ago
Last errorNone
Test with a sample payload
{"name": "Asha", "mobile": "9876543210", "city": "Pune"}
Parse (nothing is saved)Uses the saved field map.
| name | phone | city | product |
|---|---|---|---|
| Asha | 9876543210 | Pune | Design consultation |
Deleting a source keeps the leads already created.
Invitee details carried
The invitee’s name, email and phone come across, so no one types them in again.
Duplicates merged
A returning invitee who books again stays one lead, so your team never calls twice.
Routed, not dumped
Every lead goes to a pipeline and owner with your tags, or to your auto-assign rules.
Turn every Calendly booking into a CRM lead
Get Started Today- Every booking, a lead
- Pipeline & owner routing
- Duplicates merged