Popular IntoCal + Zapier workflows
- New booking → create or update a contact and deal in HubSpot, Pipedrive or Salesforce.
- New booking → add a row to Google Sheets or Airtable for reporting.
- New booking → post a message in a Slack or Microsoft Teams channel.
- Cancellation → notify the account owner and move the deal stage back.
- New booking → add the guest to a Mailchimp or ActiveCampaign sequence.
- Reschedule → update the Notion or ClickUp task due date.
Example booking payload
Zapier receives JSON similar to the example below. All timestamps are UTC ISO-8601.
{
"event": "booking.created",
"data": {
"id": "bk_7Yt2...",
"event_type": "intro-call",
"start_time": "2026-10-12T09:00:00Z",
"end_time": "2026-10-12T09:30:00Z",
"guest": { "name": "Ana Silva", "email": "ana@example.com" },
"responses": { "company": "Acme" },
"location": "ms_teams"
}
}Verifying requests
IntoCal signs every delivery with your endpoint secret and sends headers X-IntoCal-Event, X-IntoCal-Signature (sha256=...), X-IntoCal-Timestamp and X-IntoCal-Delivery. Inside Zapier you can use a Code step to compare the signature, or simply rely on the secret, unguessable hook URL.
Zapier vs native API
Zapier is the fastest way for non-developers to automate bookings. If you need to create bookings, read availability or manage event types programmatically, use the IntoCal REST API or SDK; for AI assistants, use the hosted MCP server.