Per-pair page

Calendly + Linear: design-partner calls as engineering signal.

Create Linear issues from Calendly bookings to capture user-research insights, design-partner feedback, or sales-engineering session followups in the engineering tracker.

Connect Linear and Calendly See reverse direction

Trigger app

Linear as the trigger

Workflows fire when something happens in Linear.

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.

Linear → Calendly

When something happens in Linear, do it in Calendly.

6 Linear triggers wired to 5 Calendly actions. Most-used pairing: Comment Created → Get Current User.

Calendly → Linear

Or fire it the other way around.

2 Calendly triggers wired to 8 Linear actions downstream.

See Calendly → Linear →

Popular pairings

Common Linear → 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 comment created in Linear, get current user in Calendly.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, get event in Calendly.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, list event invitees in Calendly.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, list event types in Calendly.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When new cycle in Linear, get current user in Calendly.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, get event in Calendly.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, list event invitees in Calendly.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, list event types in Calendly.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new issue in Linear, get current user in Calendly.

Fires when a new issue is created in Linear. The standard inbound hook for routing, enrichment, and SLA-aware notifications.

How it works

Connect Linear and Calendly in five steps.

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

1
Connect
Authorize Linear and Calendly
Open Tiny Command, authorize Linear and Calendly once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Linear trigger
Drop the Linear → Comment Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/linear.trigger-comment-created
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 Linear 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 Linear + Calendly.

When does Calendly + Linear belong in your stack?

When customer conversations directly drive engineering work — design-partner programs, founder-led research, or SE deep-dives. Each booking creates a tracked Linear issue with the customer context preserved.

How do I create a Linear issue from a research-interview booking?

Calendly Invitee Created filtered to event_type = "research-interview" → Linear Create Issue in a RES team, with title = "Interview: {company}", body with scheduled time and invitee details.

Can I link a Calendly-driven Linear issue to a Linear project?

Yes. Pass projectId in Create Issue. Useful when all bookings for a specific design-partner cycle should aggregate under one project for rolled-up visibility.

How do I assign the Linear issue based on Calendly event type?

Switch on event_type to choose assigneeId. Research interviews → PM. Customer onboarding → CSM. Engineering deep-dives → eng lead. One trigger, many downstream assignment paths.

Can I post post-meeting AI summary as a Linear comment?

Yes. After meeting, transcribe Zoom recording → AI summary → Linear Create Comment on the issue. Engineering sees customer signal without context-switching to the meeting tool.

How do I avoid creating Linear issues for cancelled Calendly meetings?

Either skip Create Issue until the meeting actually happens (delayed workflow that fires after end_time), or use Invitee Canceled to call Linear Archive Issue on cancelled bookings.

Other apps that pair well with Linear.

Linear + Gmail

Linear + Slack

Communication

Linear + Google Sheets

Spreadsheets & Databases

Wire Linear to Calendly in 2 minutes.

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

Try for free Request a demo

Calendly + Linear: design-partner calls as engineering signal.

Pick the way that fits your stack.

When something happens in Linear, do it in Calendly.

Or fire it the other way around.

Common Linear → Calendly workflows.

Connect Linear and Calendly in five steps.

Questions about Linear + Calendly.

Other apps that pair well with Linear.

Wire Linear to Calendly in 2 minutes.

Be the first to know what's next.