1. Integrations
  2. Asana

Asana integration: a visitor's request becomes a task in your Asana project

Agenola's Asana integration creates a task in your Asana project for a request or problem a visitor brings up, reads the task's status and tells the visitor, and adds comments and subtasks to the task. You connect it in one click with your Asana account.

How it works

A task is created by an Asana step you add to the flow, or by an action you turn on in the AI Assistant step's Integrations tab. Support requests don't land in Asana on their own.

The workspace and project are chosen on the step, not on the connection page. If your Asana account is in a single workspace, you can leave the workspace empty; if it's in several, you need to choose it on the step.

Steps cover creating, fetching, listing, searching, updating and deleting tasks; subtasks, comments, tags, the task's projects, projects and user details.

  • Tasks marked urgent move to the top of the project, so the team sees them first.
  • Asana steps run in the name of the person who made the connection: tasks are created in their name and only in projects they can access.
  • Delete steps don't run until the confirmation box on the step is ticked.
  • The “Search tasks” step uses Asana's advanced search and works only on paid Asana plans.

What it does

This list is generated from the same source as the Asana page in the dashboard: if it isn't listed here, we don't do it with Asana. Flow steps live in the flow editor under Add step → Integrations → Asana.

TaskAction · Flow step6
  • Create task

    Creates a task in the chosen project in the name of the person who connected Asana. If it's marked urgent, the task moves to the top of the project.

  • Delete task

    Deletes the task. It stays in the trash of the person who connected Asana for 30 days and can be restored from there; after that it's gone for good.

  • Get task

    Reads the task's name, status, assignee, due date, projects, tags and description.

  • List tasks

    Returns the tasks in the chosen project as a list. With “Include completed” off, only open tasks are returned.

  • Search tasks

    Finds tasks in the workspace whose name or description contains your text, latest changed first. Works only on paid Asana plans; a task created a moment ago can take up to a minute to show up in search.

  • Update task

    Changes the task's name, description, assignee, due date or status; empty fields are left unchanged.

SubtaskAction · Flow step2
  • Create subtask

    Creates a subtask under the chosen task in the name of the person who connected Asana.

  • Get subtasks

    Returns the task's subtasks as a list.

CommentAction · Flow step2
  • Add comment

    Writes a comment on the task in the name of the person who connected Asana.

  • Get comments

    Returns the task's comments as a list, latest first. Asana's own entries (such as “moved this task”) aren't included.

TagAction · Flow step2
  • Add tag

    Adds a tag from the workspace to the task.

  • Remove tag

    Removes a tag from the task; the tag stays in the workspace.

Task's projectsAction · Flow step2
  • Add to project

    Adds the task to another project; it stays in its current projects too.

  • Remove from project

    Takes the task out of the chosen project; the task isn't deleted.

ProjectAction · Flow step5
  • Create project

    Creates a project in the workspace in the name of the person who connected Asana. In a workspace set up with a company domain, a project must belong to a team; pick the team.

  • Delete project

    Deletes the project; this may not be undoable.

  • Get project

    Reads the project's name, description, owner, team and due date.

  • List projects

    Returns the projects in the workspace, or of the chosen team, as a list. Archived projects are included only with “Include archived” on.

  • Update project

    Changes the project's name, description, owner or due date, or archives or unarchives it; empty fields are left unchanged.

UserAction · Flow step2
  • Get user

    Reads an Asana user's name and email. You can also give the user by email address.

  • List users

    Returns the people in the workspace as a list.

Example conversations

A quote request becomes an Asana task

Visitor: I asked for a business quote on your website but nobody got back to me.

Agent: I'm sorry about that. Could you give me your company name and an email address we can reach you at? I'll pass it to our sales team right away.

Visitor: Atlas Logistics, purchasing@atlaslogistics.com

Agent: I've passed your request to our sales team; they'll get back to you by email.

Behind the scenes: The “Create task” step creates a task called “Quote request: Atlas Logistics” in the Sales project, with the company name and email in the description. Because “Urgent” is ticked on the step, the task moves to the top of the project.

New details are added as a comment

Visitor: One more thing: the quote should be for a fleet of 20 vehicles.

Agent: I've added that to your request; our team will see it.

Behind the scenes: The “Add comment” step writes the visitor's note on the task that was just created.

A visitor asks about their request

Visitor: I asked for a quote last week from purchasing@atlaslogistics.com. What's the status?

Agent: Your request is at the “Preparing quote” stage with our team; the quote is planned to go out by November 14.

Behind the scenes: The “Search tasks” step finds the task by the visitor's email address, and the “Get task” step reads its section and due date; the agent gives this in the visitor's language. Search needs a paid Asana plan.

Setup

  1. 1In Agenola, go to Integrations → Asana and press “Connect to Asana”.
  2. 2Grant access on Asana's consent screen.
  3. 3In the flow editor, add the “Create task” step under Add step → Integrations → Asana, and choose the project on the step.

Detailed setup: How do I connect Asana?

Permissions and where your data goes

  • Sent to Asana: the task's name, description, assignee, due date and tag; comments, subtasks and projects; the fields you set on the step.
  • Read from Asana: only when a step asks, task, comment, project and user details; for the pickers, the connected account's workspaces, teams, projects, people and tags.
  • Permissions requested: reading workspaces, teams, users and tags; reading, writing and deleting projects and tasks; reading and writing comments. Full access to your Asana account isn't requested.
  • Connection details are stored encrypted on the server. Only the owner and admins of your Agenola workspace can connect or remove it; when it's removed, Agenola's access in Asana is removed too.

Related integrations

See all integrations

Frequently asked questions

How do I tell apart tasks that came from chat?

Point the Asana steps to a separate project (such as “Incoming requests”), or choose a tag on the step; tasks are created with that tag.

We're in several Asana workspaces. What should we do?

Choose the workspace on the step; the project, people and tag lists come from that workspace. With a single workspace, you can leave the field empty.

Whose name are tasks created in?

The person's who made the connection, and only in projects they can access. Connecting with a shared team account keeps the connection working when people change roles.

Try the Asana connection on your own account

Agenola and our partners use cookies to improve the site and show you relevant ads. We count which of our ads bring visitors without using your name or email; anything more only happens if you allow it. Privacy Policy(opens in a new tab)