Asana and ClickUp, ready to switch on

A task created in the Asana project you name appears in the ClickUp list you choose with the same due date, description and owner where the names match, and later changes follow. You paste two keys in your account and we switch it on for you.

Ask us to connect it Mine is a bit different

No setup fee, cancel any month, and a person on live chat if a key doesn't work.

More with these apps: all Asana integrations · all ClickUp integrations

What moves, and when

The details you would normally get after a sales call. Here they are up front.

What	Direction	When	Rule
Task mirrored into the other tool	Asana to ClickUp	Within seconds	Into the list you choose, with the description, the dates and the assignee matched on email
And back the other way	ClickUp to Asana	Within seconds	Into the project and section you name, so neither team has to leave the tool it likes
One side owns the due date	Both ways	When it changes	You pick which, because two teams quietly moving the same deadline is worse than not syncing dates at all
Completion	Both ways	When either is closed	The twin closes too, which is the end of the weekly hunt for what is actually finished
How deep it goes	Both ways	With the parent	One level of subtasks travels; a deeper tree stays in the tool it was built in

How to set up Asana and ClickUp

A few minutes of your time, then it's ours.

Choose Asana and ClickUp

Press Connect. This pair is already selected on the checkout page at $39 a month, and there's nothing else to pick.
Pay and open your account

Card or invoice, about two minutes. The account opens with this integration waiting for its two keys.
3
Paste the Asana access token and the ClickUp API token
- Asana access token: open app.asana.com/0/developer-console, or go to Settings, then Apps, then Manage developer apps. Full Asana guide
- ClickUp API token: in ClickUp open your avatar, then Settings, then Apps. Full ClickUp guide
Each screen carries the full guide with the exact menu names, about five minutes for both.
We check both keys

Each key is checked against Asana's and ClickUp's own API the moment you paste it. If one doesn't pass, the screen says what to fix, and a person joins the chat if that isn't enough.
Create one test task, then we switch it on

A minute or two. Create a task in Asana, watch its twin appear in ClickUp, then close one and watch the other close. A person checks the setup and switches it on, within a working day.

When Asana or ClickUp changes its API, we fix it within a working day. You don't get a ticket to solve.

$39a month

Everything in the table above, with monitoring on.
Fixes when either app changes its API.
A person on live chat, weekdays 10:00 to 19:00 EET.
Custom logic beyond the table is priced separately.

Ask us to connect it

What it will cost once you can switch it on yourself. While we're in beta we connect it by hand and don't charge for it.

Ways to connect Asana and ClickUp

Two ways people connect these two, and what each one asks of you.

Zapier or MakeDovetly

Who sets it upYou, one step at a time in the scenario editorAlready built. You paste two keys and we switch it on.

Who fixes it when it breaksYou: the scenario is yours, so the fix is tooWe do, within a working day, and we watch it

What you need to knowTriggers, actions, filters and how the fields of Asana and ClickUp mapWhere the two keys are. The guide shows it.

PriceSet by the builder's plan, counted in tasks or operations$39 a month, flat, whatever the volume

Before you decide

Which one is the source of truth?

Neither, and that is why the loop guard matters. Each team works where it prefers, and the twin follows. If you would rather one side be read-only, say so and we set it that way.

Do subtasks and checklists come across?

The top level does, with title, dates and assignee. Subtasks and checklists differ so much between these two that we treat them as a custom job rather than pretending they map cleanly.

Which side should own the due date?

Pick one while connecting. Running dates both ways sounds fair and ends with two teams quietly moving the same deadline, so we usually let the delivery side own it and the other side follow.

Anything to know about Asana?

A personal access token acts as your user, so tasks are created in your name and only in projects that user can see.

Anything to know about ClickUp?

The personal token acts as you, so tasks the integration creates show your name as their creator. A user made for the integration keeps that tidy.

What if mine is a bit different?

Tell us what should go where in plain words. Small changes to the rules above are usually free; bigger ones we price within a working day and build into the same account.