Calendly
Bookings as triggers, with the full invitee payload
Calendly is the booking funnel for most modern sales and customer teams, and on Tiny Command the two events that matter come through as first-class triggers. Invitee Created fires the moment someone books, payload includes the invitee email, name, phone, scheduled time, time zone, event type, and every answer to the custom questions on the booking form. Invitee Canceled fires when they cancel, with the reason if they left one. Five actions cover the read side: Get Current User, Get Event, List Event Types, List Events, List Event Invitees. Authorize via Calendly's OAuth at the user or organization level. Common patterns: a demo booking on Calendly fires the trigger, AI pre-fills a meeting brief from the LinkedIn URL in the booking questions, HubSpot gets a new contact, Zoom creates the meeting, and Slack pings the rep. Cancellations route to a different workflow that asks for a reason and re-engages with availability.
Workflows start when Calendly does.
2 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a Calendly meeting is canceled by the invitee or host. Use to clean up CRM activity, release Zoom resources, or prompt a reschedule.
Fires when someone schedules a meeting via Calendly. The standard hook for piping booked meetings into your CRM, sending prep, or auto-routing to the right team.
Do anything Calendly can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Get Current User | Returns the authenticated user's info, including the user URI required for most other Calendly API calls. Standard connection-check action. |
| Get Event | Returns details of a scheduled Calendly event with start/end time, event type, and location. Used to enrich a trigger payload before posting downstream. |
| List Event Invitees | Lists invitees for a scheduled Calendly event with their name, email, status, and answers to custom questions. Used to enrich the booking with the invitee details. |
| List Event Types | Lists available event types (meeting templates) for the user, with their booking URLs and durations. Used to populate a meeting-type picker. |
| List Events | Lists scheduled events for the authenticated Calendly user with filters for date range and status. Used for daily-roster emails or for syncing into a BI tool. |
Pre-built Calendly workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Calendly once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Calendly field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Calendly integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Calendly to Tiny Command?
What Calendly triggers does Tiny Command support?
What Calendly actions can I run from a workflow?
Is the Calendly integration real-time?
Do I need to write code to use Calendly with Tiny Command?
How much does the Calendly integration cost?
More calendar & scheduling apps people connect.
Same category as Calendly, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Calendly.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
