Zendesk and Asana integration

Whalesync syncs Zendesk and Asana both ways. Tickets and organizations become tasks in the projects you pick, and moving a task to another section updates a field agents see in Zendesk.

Zendesk
Asana
Use cases

What you can do with Zendesk and Asana

Support with engineering

Escalate bug tickets to the engineering project

Set a Zendesk ticket's Engineering status to Triage, and it becomes a task in the Triage section of the engineering team's Asana project, with the customer's first message as its description. As engineers move the task on to In progress and Fixed, the ticket's field follows, so the agent knows when to write back to the customer.

Syncs TicketsTasks (one table per project)
Each card is a Zendesk ticket, numbered as in Zendesk. Its section is the ticket's Engineering status, synced both ways, and the assignee is Asana's own.
Customer onboarding

Run onboarding with one task per customer

Give a new Zendesk organization an Onboarding stage, and it gets a task in your Asana onboarding project, in the section of that name. The customer success manager works through the task's subtasks and moves it from Kickoff to Live, and the organization's stage and go-live date stay current in Zendesk, where agents check them before they answer a new customer.

Syncs OrganizationsTasks (one table per project)
The task is a Zendesk organization. Its section and due date are the organization's Onboarding stage and go-live date, and the subtasks are Asana's own.
Finance

Approve refunds in Asana, answer them in Zendesk

Set a refund ticket's Refund status to Review, and it becomes a task in finance's Asana project, with the amount in a number field. Finance moves it to Approved, then Paid, and the ticket's Refund status changes with it, so the agent can confirm the refund to the customer without messaging finance.

Syncs TicketsTasks (one table per project)
Each row is a Zendesk ticket in a refunds view. The amount and refund status sync with the ticket's task in Asana.
What syncs

Everything that syncs

Each card is something you can sync between Zendesk and Asana.

  • Zendesk Tickets Two-way
  • Zendesk Users Two-way
  • Zendesk Organizations Two-way
  • Zendesk Custom objects Two-way
  • Zendesk Agents Into Asana
  • Zendesk Groups Into Asana
  • Zendesk Brands Into Asana
  • Asana Tasks (one table per project) Two-way
  • Asana Projects Into Zendesk
  • Asana Tags Into Zendesk
  • Asana Users Into Zendesk
Step-by-step guide

How to sync Zendesk and Asana

Step 1: Open a new sync with Zendesk and Asana

Start from New sync in Whalesync, and pick Zendesk and Asana.

Step 2: Authorize Zendesk from its subdomain

Give Whalesync only the subdomain, the word before .zendesk.com, and log in to Zendesk in the same tab when it asks. Sign in as an admin: if Zendesk later refuses an action, Whalesync's fix is to reconnect as one.

Step 3: Sign in to Asana and choose the projects

Sign in with Asana, which asks for full permissions because a narrower grant can't list a project's sections, or paste a personal access token. Pick the workspace and the projects to sync. Whalesync acts as you in Asana, so it sees the projects you can see and nothing else.

Step 4: Line up sections with Zendesk dropdowns

Whalesync creates no Asana sections and no Zendesk fields or dropdown options. Give tickets an Engineering status dropdown whose options read exactly like the engineering project's sections, such as Triage, In progress, and Fixed, and do the same for Refund status on tickets and Onboarding stage on organizations. Asana's number and other custom fields, like the refund amount, need a paid Asana plan.

Step 5: Pair tickets and organizations with projects

Pair Tickets with the engineering project, map Engineering status to Section, Subject to Name, Description to Description, and the Zendesk Record ID to a text field for the ticket number, and add a filter so only tickets whose Engineering status isn't empty sync. Pair Organizations with the onboarding project the same way, on Onboarding stage. A table pairs once per sync, so refunds take a second sync, filtered on Refund status. Keep each project for these tasks alone: a task someone adds there by hand passes the filter too, and becomes a Zendesk ticket or organization. Automap sends an AI model only the field names and types, not your tickets, to suggest pairs, and you keep the right ones and map the rest by hand.

Step 6: Check your triggers, then switch the sync on

An update Whalesync makes to a ticket runs your Zendesk triggers, as an agent's update would, and a new ticket can email its requester. Look over the triggers that react to the fields you mapped, then activate the sync.

Compare

3 ways to connect Zendesk and Asana

  • Asana's app for Zendesk

    Best when agents escalate tickets one at a time from the sidebar, and seeing the task's status there is enough.

    • Made by Asana: create a task, or link one, from the Zendesk ticket sidebar
    • Shows the task's status and owner in Zendesk, and the ticket's title, number, and assignee in Asana (Asana)
    • Asana rules can add a comment to the ticket when the task changes
  • Zapier

    Best when you want a task for every new ticket in a view, and nothing needs to come back.

    • Zendesk counts as a premium app, so Zaps that use it need a paid plan
    • One-way Zaps only: Zapier doesn't do two-way sync
    • Can post comments on Asana tasks and Zendesk tickets, which Whalesync doesn't sync
  • Whalesync

    Best when support and the team doing the work should see the same status, each from its own app.

    • An Asana section and a Zendesk field move together
    • Filtered tickets or organizations become tasks
    • Charged on records in sync; updates are unlimited

Asana's app for Zendesk and Zapier checked against their own pages in November 2026.

FAQ

Frequently asked questions

Does Asana have a Zendesk integration?

Yes. Asana for Zendesk, made by Asana, creates or links a task from a ticket and shows each side's status to the other. Zapier runs one-way automations, and Whalesync keeps tickets or organizations and their tasks in sync both ways.

Can I create Asana tasks from Zendesk tickets automatically?

Yes. Pair Zendesk Tickets with an Asana project and filter on a mapped field agents set, such as an Engineering status dropdown, so only those tickets become tasks. A ticket reaches the project within seconds of the agent setting it.

Can moving an Asana task update the Zendesk ticket?

Yes, through a Zendesk dropdown mapped to the task's Section, with options named exactly like the project's sections, since Whalesync creates neither. Zendesk doesn't accept changes to a closed ticket, so a task moved after its ticket has closed shows up as a sync issue instead.

Do Asana and Zendesk sync instantly?

Yes, for tasks, tickets, users, and organizations: Asana and Zendesk both tell Whalesync when one changes, and the change reaches the other app within seconds. Zendesk custom object records and an organization's notes, details, and domains send no such notice, so edits to them wait for a full scan, daily by default.

Can Zendesk comments sync to Asana tasks?

No. A ticket's first message becomes the task's description when the task is created, but later comments, attachments, and Asana's task comments don't sync. Asana's own integration can post an internal note on the ticket through a rule.

More integrations

Other apps to connect

Connect your tools in minutes