Skip to content
Per-pair page

Asana + Linear: PM team and engineering team, finally in sync.

Create Linear issues from Asana tasks, mirror Linear status back to Asana. PM teams plan in Asana; engineering teams ship in Linear; nobody re-enters work.

Trigger app
Asana as the trigger

Workflows fire when something happens in Asana.

Action app
Linear as the action

Workflows do something in Linear, instantly.

Both directions

Pick the way that fits your stack.

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

AsanaLinear

When something happens in Asana, do it in Linear.

1 Asana triggers wired to 8 Linear actions. Most-used pairing: New TaskAdd Comment.

LinearAsana

Or fire it the other way around.

6 Linear triggers wired to 15 Asana actions downstream.

See LinearAsana
Popular pairings

Common Asana → Linear workflows.

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

Showing 4 of 8 combinations
How it works

Connect Asana and Linear in five steps.

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

  1. 1
    Connect
    Authorize Asana and Linear

    Open Tiny Command, authorize Asana and Linear once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a Asana trigger

    Drop the Asana → New Task trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/asana.trigger-task-created
  3. 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. 4
    Action
    Add the Linear action

    Drop the Linear → Add Comment action below it. Map fields from the Asana payload into the Linear inputs.

    linear.create-comment
  5. 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 Asana + Linear.

How does the Asana + Linear sync work in practice?
Asana Task moved to "In Dev" → Linear Create Issue with title and description from the Asana task → save the Linear identifier to an Asana custom field. Linear status changes flow back as Asana custom field updates.
Can I avoid creating duplicate Linear issues?
Yes. Use the Asana custom field "Linear ID" as the upsert guard. The workflow only creates a Linear issue if the custom field is empty; otherwise it calls Update Issue.
How do I map Asana sections to Linear projects?
Maintain a lookup of asana_section_gid → linear_project_id. The workflow uses the lookup at Create Issue time to put the issue in the right Linear project.
Can I sync Asana priority into Linear priority?
Yes. Linear priorities are integers (1=Urgent, 2=High, 3=Medium, 4=Low). Map your Asana priority enum to the right integer via a Switch node before Create Issue.
How do I include Asana comments in the Linear issue description?
Get Stories from Asana, concatenate user comments (skip system events), and append to the Linear issue description as Markdown blockquotes. Or post each comment as a Linear comment after creation.
Which side owns assignee, status, and dates?
Linear owns assignee and status (it's an engineering decision). Asana owns the planning fields (priority from PM, due date from stakeholder commitments). Each side's update flows one direction.
Related

Other apps that pair well with Asana.


Wire Asana to Linear in 2 minutes.

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