Connect ClickUp and Linear
Start a client’s workflow in ClickUp and act in Linear, or the other way round, on the client’s own accounts.
Each app by itself: ClickUp integration and Linear integration, with how to connect it, its scopes and its limits.
What the pair is used for
- An account team working in ClickUp can hand requests to developers in Linear, each task added to a chosen list opening a Linear issue with the task’s name as its title.
- New Linear issues in a team, and issues that change status, can appear as tasks in a ClickUp list, so the people talking to the client see engineering work as it moves.
- Linear’s “Create an issue” returns the new issue’s identifier and link, which a “Update a task” step can write back into the ClickUp task’s description.
Every way ClickUp and Linear join
A workflow starts from a trigger in one app and runs a step in the other, on the client’s accounts. Where the library has a starter for it, it installs that pairing into a client switched off; any other pairing is two steps on the canvas.
From ClickUp to Linear
| When this happens in ClickUp | This runs in Linear | How fast | Starter |
|---|---|---|---|
| A task is added to a list | Create an issue | Within 5 minutes | Install the starter |
| A task is added to a list | Update an issue | Within 5 minutes | Two steps on the canvas |
| A task changes status | Create an issue | Within seconds | Two steps on the canvas |
| A task changes status | Update an issue | Within seconds | Two steps on the canvas |
From Linear to ClickUp
| When this happens in Linear | This runs in ClickUp | How fast | Starter |
|---|---|---|---|
| An issue is opened | Create a task | Within seconds | Install the starter |
| An issue is opened | Update a task | Within seconds | Two steps on the canvas |
| An issue changes status | Create a task | Within seconds | Install the starter |
| An issue changes status | Update a task | Within seconds | Two steps on the canvas |
Set up the starter
Create an issue in Linear when a task is added to a list in ClickUp
- 1Install the starter into the client from Templates → Library. It lands switched off.
- 2Connect the client’s ClickUp, for “A task is added to a list”
- 3Connect the client’s Linear, for “Create an issue”
- 4Fill in ClickUp: List ID (For example the number in the list’s URL)
- 5Fill in Linear: Team ID (For example the team’s UUID)
- 6Switch it on. Within 5 minutes: ClickUp is checked every 5 minutes.
What it produces
The Linear step as it runs for an example client, Lakeview Consulting, when Emma Collins asks for a consultation: each value the starter fills in.
- Team ID
- Consultations
- Title
- Consultation with Emma Collins
Setup notes for this pair
- The task-to-issue starter fills the team and title; the issue-to-task starters fill only the list, so give the task a name from the issue’s title or identifier.
- A list and a team wired both ways echo each other, every copy arriving as new on the far side. Keep one direction per list and team.
Field mapping, starter by starter
Each value a starter’s step is given, and where it comes from. Words in brackets are filled in when it runs; change any of it after installing.
Create an issue for new tasks
Create an issue in Linear when a task is added to a list in ClickUp
| Linear value | Filled from |
|---|---|
| Team ID | [Linear: Team ID] |
| Title | [the task’s name, from ClickUp] |
Create a task for new issues
Create a task in ClickUp when an issue is opened in Linear
| ClickUp value | Filled from |
|---|---|
| Name | [the issue’s title, from Linear] |
| List ID | [ClickUp: List ID] |
Create a task for issue status changes
Create a task in ClickUp when an issue changes status in Linear
| ClickUp value | Filled from |
|---|---|
| Name | [the issue’s title, from Linear] |
| List ID | [ClickUp: List ID] |
ClickUp and Linear and their logos are trademarks of their owners, used here only to say what Thrum works with; no endorsement is implied.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.