Per-pair page

Calendly + Zendesk: bookings tied to support tickets.

Create Zendesk tickets from Calendly bookings (for high-touch support call follow-ups), or trigger Calendly booking links from Zendesk replies.

Connect Zendesk and Calendly See reverse direction

Trigger app

Zendesk as the trigger

Workflows fire when something happens in Zendesk.

See all 6 triggers →

Action app

Calendly as the action

Workflows do something in Calendly, instantly.

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Zendesk → Calendly

When something happens in Zendesk, do it in Calendly.

6 Zendesk triggers wired to 5 Calendly actions. Most-used pairing: Ticket Assigned → Get Current User.

Calendly → Zendesk

Or fire it the other way around.

2 Calendly triggers wired to 17 Zendesk actions downstream.

See Calendly → Zendesk →

Popular pairings

Common Zendesk → Calendly workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 30 combinations

When ticket assigned in Zendesk, get current user in Calendly.

Fires when a ticket is assigned (or reassigned) to an agent in Zendesk. Use to ping the assignee, start an SLA clock, or audit workload balance.

When ticket assigned in Zendesk, get event in Calendly.

Fires when a ticket is assigned (or reassigned) to an agent in Zendesk. Use to ping the assignee, start an SLA clock, or audit workload balance.

When ticket assigned in Zendesk, list event invitees in Calendly.

Fires when a ticket is assigned (or reassigned) to an agent in Zendesk. Use to ping the assignee, start an SLA clock, or audit workload balance.

When ticket assigned in Zendesk, list event types in Calendly.

Fires when a ticket is assigned (or reassigned) to an agent in Zendesk. Use to ping the assignee, start an SLA clock, or audit workload balance.

When ticket commented in Zendesk, get current user in Calendly.

Fires when a comment (public or internal) is added to a Zendesk ticket. Common use: notify Slack of customer replies, log activity, or mirror conversations into a CRM.

When ticket commented in Zendesk, get event in Calendly.

Fires when a comment (public or internal) is added to a Zendesk ticket. Common use: notify Slack of customer replies, log activity, or mirror conversations into a CRM.

When ticket commented in Zendesk, list event invitees in Calendly.

Fires when a comment (public or internal) is added to a Zendesk ticket. Common use: notify Slack of customer replies, log activity, or mirror conversations into a CRM.

When ticket commented in Zendesk, list event types in Calendly.

Fires when a comment (public or internal) is added to a Zendesk ticket. Common use: notify Slack of customer replies, log activity, or mirror conversations into a CRM.

When new ticket in Zendesk, get current user in Calendly.

Fires when a new support ticket is created in Zendesk, across any channel (email, web form, chat, API, social). The standard inbound hook for AI triage and routing.

How it works

Connect Zendesk and Calendly in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Zendesk and Calendly
Open Tiny Command, authorize Zendesk and Calendly once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Zendesk trigger
Drop the Zendesk → Ticket Assigned trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/zendesk.trigger-ticket-assigned
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Calendly action
Drop the Calendly → Get Current User action below it. Map fields from the Zendesk payload into the Calendly inputs.
calendly.get-current-user
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Zendesk + Calendly.

When is Calendly + Zendesk useful?

When customer success or escalation calls are part of the support workflow. Calendly handles scheduling; Zendesk keeps the support history. The pair makes sure both sides know about each call.

How do I create a Zendesk ticket from a Calendly booking?

Calendly Invitee Created → Zendesk Find or Create User by email → Zendesk Create Ticket with subject = "Calendly meeting scheduled: {event_type}", body with scheduled time and intake answers.

Can I add Calendly bookings to existing Zendesk tickets?

Yes. If the invitee already has an open ticket, look it up by email and Zendesk Add Comment (public=false) with the booking details. Avoids spawning a parallel ticket.

How do I make a Calendly link available in Zendesk macros?

Maintain a Zendesk macro that includes the right Calendly booking link per event type. Agents trigger the macro mid-ticket to send the customer a custom booking link in the support response.

Can a Calendly cancellation update the Zendesk ticket status?

Yes. Calendly Invitee Canceled → look up linked Zendesk ticket → Zendesk Update Ticket with status = "pending" (or a custom status). Agent sees the cancellation in their queue.

How do I track meeting outcomes back to the Zendesk ticket?

Scheduled workflow after meeting end → AI summarize the recording (if available) → Zendesk Add Comment (public=false) with the meeting outcome and action items. Agent has full context in one place.

Other apps that pair well with Zendesk.

Zendesk + Gmail

Zendesk + Slack

Communication

Zendesk + Google Sheets

Spreadsheets & Databases

Wire Zendesk to Calendly in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo

Calendly + Zendesk: bookings tied to support tickets.

Pick the way that fits your stack.

When something happens in Zendesk, do it in Calendly.

Or fire it the other way around.

Common Zendesk → Calendly workflows.

Connect Zendesk and Calendly in five steps.

Questions about Zendesk + Calendly.

Other apps that pair well with Zendesk.

Wire Zendesk to Calendly in 2 minutes.

Be the first to know what's next.