Per-pair page

ClickUp + Linear: bridge product teams to engineering teams.

Sync ClickUp tasks to Linear issues for engineering execution. Product/marketing teams live in ClickUp; engineering ships from Linear.

Connect Linear and ClickUp See reverse direction

Trigger app

Linear as the trigger

Workflows fire when something happens in Linear.

See all 6 triggers →

Action app

ClickUp as the action

Workflows do something in ClickUp, instantly.

See all 9 actions →

Both directions

Pick the way that fits your stack.

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

Linear → ClickUp

When something happens in Linear, do it in ClickUp.

6 Linear triggers wired to 9 ClickUp actions. Most-used pairing: Comment Created → Add Comment.

ClickUp → Linear

Or fire it the other way around.

6 ClickUp triggers wired to 8 Linear actions downstream.

See ClickUp → Linear →

Popular pairings

Common Linear → ClickUp workflows.

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

Showing 9 of 54 combinations

When comment created in Linear, add comment in ClickUp.

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, create task in ClickUp.

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, delete task in ClickUp.

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 task in ClickUp.

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, add comment in ClickUp.

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, create task in ClickUp.

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, delete task in ClickUp.

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 task in ClickUp.

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, add comment in ClickUp.

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 ClickUp in five steps.

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

1
Connect
Authorize Linear and ClickUp
Open Tiny Command, authorize Linear and ClickUp 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 ClickUp action
Drop the ClickUp → Add Comment action below it. Map fields from the Linear payload into the ClickUp inputs.
clickup.create-comment
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 + ClickUp.

How does ClickUp + Linear sync work in practice?

ClickUp Task moved to "In Dev" status → Linear Create Issue with title and description from the ClickUp task → save Linear identifier in a ClickUp custom field. Linear status changes flow back as ClickUp custom field updates.

How do I avoid creating duplicate Linear issues?

Use the "Linear ID" custom field as the upsert guard. The workflow only creates a Linear issue if the field is empty; otherwise it calls Update Issue.

How do I map ClickUp spaces/lists to Linear projects?

Maintain a (clickup_list_id → linear_project_id) lookup. The workflow uses it at Create Issue time. Different ClickUp lists map to different Linear projects, all from one workflow.

Can I sync ClickUp priority into Linear priority?

Yes. Linear priorities are integers (1=Urgent, 2=High, 3=Medium, 4=Low). Switch on ClickUp priority value to map to the right integer before Create Issue.

How do I include ClickUp comments in the Linear issue description?

Get Task Comments from ClickUp, concatenate user comments (skip system events), and append as Markdown blockquote in the Linear issue description. Or post each as a Linear comment after creation.

Which side owns assignee, status, and dates?

Linear owns engineering decisions (assignee, status). ClickUp owns planning fields (priority from PM, due date from stakeholder). Each direction flows one way.

Other apps that pair well with Linear.

Linear + Gmail

Linear + Slack

Communication

Linear + Google Sheets

Spreadsheets & Databases

Wire Linear to ClickUp in 2 minutes.

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

Try for free Request a demo

ClickUp + Linear: bridge product teams to engineering teams.

Pick the way that fits your stack.

When something happens in Linear, do it in ClickUp.

Or fire it the other way around.

Common Linear → ClickUp workflows.

Connect Linear and ClickUp in five steps.

Questions about Linear + ClickUp.

Other apps that pair well with Linear.

Wire Linear to ClickUp in 2 minutes.

Be the first to know what's next.