Datapipe
Marketers
Track bookings next to the campaigns behind them.
Read & reportControlled changes
See your Calendly numbers in Claude.
Read booking and routing reports, then change event-type wording and settings, cancellations and no-show marks for the connected user.
- Every response or booking in a sheet that refreshes itself
- Weekly results without exporting from Calendly
- Ask an AI assistant to summarize what people told you
ClaudeUpdated November 2026
| Event name | Event status | Starts at (UTC) |
|---|---|---|
| Discovery call | active | 2026-10-27T14:00:00Z |
| Team demo | active | 2026-10-28T16:30:00Z |
| Project review | canceled | 2026-10-29T10:00:00Z |
- SetupSign in or paste a key
- Reads114 report fields across 9 datasets
- Changes5 change actions
- RefreshDaily to every 15 minutes
Who uses Datapipe with Calendly
Sales teams
See booked calls and routing form answers in one place.
Team leads
See bookings, cancellations and reschedules by host and event type.
What you can do with Calendly
Read and report
Read eight additional datasets covering event details and invitee cancellation/reschedule/no-show metadata, event types, current organization members, routing forms and submissions, availability schedules and the connected user profile.
- Calendly events
- Scheduled event details
- Invitees for an event
- Event type inventory
- and 5 more
Controlled changes
- Update approved event type text
- Change an event type's duration, color, language or location
- Turn an event type on or off
- Cancel a booked meeting
- Mark an invitee as a no-show or clear it
Changes stay off until you allow them. Allowed changes apply to Calendly right away, and history keeps the values before and after.
Full read details
Dates select event starts; explicit resource and configuration reads use their own current-state rules.
Examples for your team
Review invitees without mixing event counts
Choose one event involving the connected user.
- Scheduled refresh
- Latest Calendly data
- Updated report
Limit: Read invitee answers, attribution tracking, cancellations and replacement invitee references while preserving one row per invitee.
Review routing and availability with context
Read a form's available submissions, including responses without a booked event.
- Scheduled refresh
- Latest Calendly data
- Updated report
Limit: Review user availability rules separately; they do not promise that a slot is currently bookable.
Clarify a client booking page
A teammate sets clearer name or plain text description wording on an active one-on-one event type owned by the connected user.
- Allowed
- Applied
- Recorded
Limit: The owner selects writable fields, and history keeps the before/after text. Description edits replace formatting; availability, booked events and pricing stay outside this action.
Fix things in Calendly without opening it
Spot it, fix it
See the problem in your report, then make the fix in Datapipe instead of opening Calendly, finding the record and retyping it.
More people can help
Teammates and AI tools you allow can make changes without getting edit access to Calendly.
You decide what can change
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
Jobs you can stop doing by hand in Calendly
Update approved event type text
Clarify event types with many no-shows
TodayRewrite the event description in Calendly and hope people read it before booking.
With DatapipeYour Calendly report shows which event types get no-shows. ChatGPT writes a clearer description, and the booking page updates. History keeps the old text.
Rename event types so clients book correctly
TodayOpen each event type in Calendly, rename it and check the booking page still makes sense.
With DatapipeA teammate sets the new name, and history records the before and after. Duration, availability and location stay as they are.
Add prep notes to an event description
TodayEmail each invitee the same prep instructions after they book.
With DatapipeWrite a plain text description that says what to bring. It replaces the current description and its formatting, and history keeps the old text.
Exactly what this can change
Updates owner-selected name and plain text description on an active one-on-one event type owned by the connected user. Description edits replace formatting. Booking-page wording can change immediately and connected workflows may react. Admin-managed types, booked events, duration, availability, location, pricing, visibility, creation and deletion are excluded. Outside edits can race execution; uncertain results never retry automatically.
The owner, an admin or a project manager picks the supported writable fields for this action before anyone can make changes.
Change an event type's duration, color, language or location
Change a call from 30 to 45 minutes
TodayOpen the event type in Calendly and change the duration.
With DatapipeSet the new duration from Datapipe. The booking page changes straight away. Meetings already booked keep their length.
Switch an event type to Zoom
TodayEdit the location in Calendly and check the booking page.
With DatapipeSet the new location. It replaces the current location options, and history keeps the old value.
Exactly what this can change
Changes the duration, color, booking page language or meeting location of one one-on-one event type owned by the connected Calendly user. A new location replaces every current location option. Video locations need that app connected in Calendly. The booking page changes immediately; meetings already booked keep their details. Admin-managed and team event types are excluded.
Supported fields: Duration (minutes), Color (hex code, like #0069ff), Booking page language, Location, Address, location text or phone number.
Turn an event type on or off
Pause bookings during a holiday
TodayRemember to switch the event type off in Calendly, and back on later.
With DatapipeTurn it off from Datapipe. Meetings already booked stay booked.
Reopen an event type for a new campaign
TodayFind the event type and switch it on.
With DatapipeTurn it on from Datapipe.
Exactly what this can change
Turns one one-on-one event type owned by the connected Calendly user on or off. Turning it off stops new bookings straight away and its booking link shows as unavailable; meetings already booked stay booked. Turning it on lets people book it again.
Supported fields: Event type.
Cancel a booked meeting
Cancel a meeting the client asked to drop
TodayOpen the meeting in Calendly, cancel it and type a reason.
With DatapipeCancel it from Datapipe with a reason. Calendly emails the invitees right away, so cancellations can be set to need approval first.
Cancel a duplicate booking
TodaySpot the duplicate in your calendar and cancel it in Calendly.
With DatapipeThe meetings report shows the duplicate. Cancel that exact meeting from Datapipe.
Exactly what this can change
Cancels one upcoming meeting hosted by the connected Calendly user. Calendly emails every invitee a cancellation notice with the reason you enter, removes the calendar event and may run your Calendly workflows. A cancelled meeting can't be restored; invitees would have to book again.
Supported fields: Change, Reason shown to invitees.
Mark an invitee as a no-show or clear it
Mark invitees who didn't attend
TodayOpen each past meeting in Calendly and mark the no-show.
With DatapipeMark the no-show for each invitee from the report. Your no-show rate stays accurate.
Clear a no-show marked by mistake
TodayFind the meeting and undo the mark.
With DatapipeRemove the mark from Datapipe.
Exactly what this can change
Marks one invitee of a meeting the connected user hosted as a no-show, or removes that mark. Calendly doesn't email the invitee for this, but your Calendly workflows or connected apps that watch no-shows may react. Only meetings that have started and weren't cancelled can be marked.
Supported fields: No-show.
Update approved event type textEvent type · 30 min call · made by Jordan Blake
| Field | Before | After |
|---|---|---|
| Name | 30 min call | 30 min project intro call |
You control who can change what
- A change is allowed for this data source
- A teammate or AI tool makes it
- It applies right away, or waits for approval if you set that
- Recorded with the values before and after
Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?
Provider rules and limits
Provider permissions still apply, and automations in Calendly may react to changes.
Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.
Before you connect
What you need
Connect Calendly from Data sources using provider sign-in or a personal access token.
Read and write
Read access for reports. The 5 change actions need edit access in Calendly and stay off until the owner, an admin or a project manager allows them.
Limits and exclusions
Only the event report uses event start dates to select rows; invitees, routing submissions and current configuration ignore report dates. Reschedule references do not deduplicate people.
Full details and limits
Eight additional datasets join the original event report. Only the event report uses event start dates to select rows; invitees, routing submissions and current configuration ignore report dates. Explicit invitee reports require an event involving the connected user; routing forms and members belong to that user's current organization. Organization role, paid-plan features and read permissions affect availability. Routing submissions include provider-available responses without inventing a historical retention guarantee. Reschedule references do not deduplicate people. Availability schedules describe configuration, not free/busy history or live bookable slots. Existing sign-ins may need reconnect consent for the added reads. This expansion does not book, cancel, reschedule or invite anyone.
Reports you can build
9 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
- Calendly events
- Scheduled event details
- Invitees for an event
- Event type inventory
- Organization members
- Routing form inventory
- Submissions for a routing form
- User availability schedules
- Connected user profile
What each dataset reports
- Calendly events
Meetings on your calendar.
- Scheduled event details
Events involving the connected user, selected by event start time within the requested UTC dates. Includes active and canceled events; cancellation and modification times do not select the reporting period. Permissions and Calendly plan affect availability. Missing values remain null, IDs remain canonical URI strings and collections stay JSON; separate datasets are not automatically joined.
- Invitees for an event
Current accessible records, independent of report dates; dates do not reconstruct earlier state. Choose one event involving the connected user. Each row is one invitee, including current cancellation, reschedule lineage, no-show metadata, booking answers and tracking. Reschedule links are references to other invitee records, not deduplicated people. Payment data and action-capable cancel/reschedule links are excluded. Permissions and Calendly plan affect availability. Missing values remain null, IDs remain canonical URI strings and collections stay JSON; separate datasets are not automatically joined.
- Event type inventory
Current accessible records, independent of report dates; dates do not reconstruct earlier state. Personal, team and organization event types associated with the connected user; active and inactive types are included when accessible. Configured durations are minutes. Permissions and Calendly plan affect availability. Missing values remain null, IDs remain canonical URI strings and collections stay JSON; separate datasets are not automatically joined.
- Organization members
Current accessible records, independent of report dates; dates do not reconstruct earlier state. Memberships in the connected user's current organization. Organization-wide access depends on the user's role and consent; this does not invite, remove or change members. Permissions and Calendly plan affect availability. Missing values remain null, IDs remain canonical URI strings and collections stay JSON; separate datasets are not automatically joined.
- Routing form inventory
Current accessible records, independent of report dates; dates do not reconstruct earlier state. Forms in the connected user's current organization, with current non-deleted questions. Routing features can require an eligible paid plan. Permissions and Calendly plan affect availability. Missing values remain null, IDs remain canonical URI strings and collections stay JSON; separate datasets are not automatically joined.
- Submissions for a routing form
Current accessible records, independent of report dates; dates do not reconstruct earlier state. Choose a form in the connected user's current organization. Lists provider-available submissions, including responses that did not book an event. The API has no creation-date filter for this collection; report dates do not select submissions. Each row retains question/answer IDs, result and submitter reference. Permissions and Calendly plan affect availability. Missing values remain null, IDs remain canonical URI strings and collections stay JSON; separate datasets are not automatically joined.
- User availability schedules
Current accessible records, independent of report dates; dates do not reconstruct earlier state. Configured weekly rules and date overrides for the connected user, in each schedule's timezone. This is availability configuration, not a list of currently bookable slots or free/busy calendar history. Permissions and Calendly plan affect availability. Missing values remain null, IDs remain canonical URI strings and collections stay JSON; separate datasets are not automatically joined.
- Connected user profile
Current accessible records, independent of report dates; dates do not reconstruct earlier state. Permissions and Calendly plan affect availability. Missing values remain null, IDs remain canonical URI strings and collections stay JSON; separate datasets are not automatically joined.
Metrics and dimensions
114 report fields across 9 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Send Calendly data anywhere
Google SheetsA sheet that refreshes every morning.
Data StudioCharts that read the same numbers.
BigQueryA warehouse table for the same columns.
Excel / CSVA Drive file you can open in Excel.ClaudeAsk Claude about these numbers in a sentence.
ChatGPTAsk ChatGPT about these numbers in a sentence.
APIRead the same rows from your own tool.Don't see yours? Use CSV or APIDownload the rows, or read them from your own tool.Ask AI about your data
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also make allowed Calendly changes. They can never widen their own access.
Which event types in Calendly had the most canceled meetings last month?
Discovery Call had 14 of 62 meetings canceled (23%), well above the 8% average for the other event types.
Better than exporting by hand
- It refreshes on its own, so nobody pastes in a new export.
- The same numbers can be split by who they came from.
- You can keep a row per day instead of one lump sum.
- See whether it ran on a phone, a feed, or another placement.
- People and the way you reach them can be their own rows.
What can you do with this data?
Explore all use cases →Start from a goal
Scheduled event details
Events involving the connected user, selected by event start time within the requested UTC dates.
Use this template →Invitees for an event
Current accessible records, independent of report dates; dates do not reconstruct earlier state.
Use this template →Event type inventory
Current accessible records, independent of report dates; dates do not reconstruct earlier state.
Use this template →Organization members
Current accessible records, independent of report dates; dates do not reconstruct earlier state.
Use this template →How it works
Connect Calendly from Data sources using provider sign-in or a personal access token.
Pick where it goes. This one sends the numbers to Claude.
Choose a dataset and its fields, then refresh on a schedule. Select an event or routing form for its detailed report.
Sample report
Sample scheduled-event report. Each row is one event selected by its UTC start date. Invitee answers and routing submissions have separate reports.
| Event name | Event status | Starts at (UTC) | Active invitees | Cancellation reason |
|---|---|---|---|---|
| Discovery call | active | 2026-10-27T14:00:00Z | 1 | — |
| Team demo | active | 2026-10-28T16:30:00Z | 3 | — |
| Project review | canceled | 2026-10-29T10:00:00Z | 0 | Timing changed |
Sample numbers, so you can see the shape. Your report uses your accounts.
Works well with Calendly
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Questions
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.
No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected Calendly account. Nobody else gets a Calendly login from this.
Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.
Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.
Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that Calendly received it, the request is marked Uncertain and is never retried automatically, so you can check Calendly first.
Yes. Datapipe reads the reports on this page and can make 5 kinds of change: update approved event type text; change an event type's duration, color, language or location; turn an event type on or off; cancel a booked meeting; mark an invitee as a no-show or clear it. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.
This page lists 114 report fields across 9 datasets. You pick the columns when you build the report.
Available rows depend on the connected account, selected report type, its date rules and provider limits. Current-inventory reports show current records rather than earlier historical states.
One for each Calendly account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Try Calendly with sample data first
Build the report first, then add Calendly when you are ready.