Asana setup guide

Agents keep projects moving: they read, create and update tasks and issues where your team works.

Ways to connect

Company admins connect apps, on the Integrations page in Everdeck: open Asana, choose one of the ways below, follow its steps and fill in its fields. Everdeck checks what you enter before it saves anything, and asks you to confirm it’s you (your second factor) before you type any secret. How connecting works.

Asana can be connected 2 ways. Where there’s a key or token to paste, that’s usually the quickest.

Personal access token

API key.

1. Sign in to Asana as the user the agent should act as (a dedicated member keeps its work easy to spot).
2. Open the developer console at https://app.asana.com/0/my-apps and create a personal access token.
3. Paste the token into the form.
4. Optional, to start work when a task changes or someone comments: once connected, set up the Asana trigger you want on Everdeck's Intake page and copy the address it gives you. Asana makes webhooks only through its API, so run this with your token, the project's ID (the number after /project/ in the project's address) and that address: curl -X POST https://app.asana.com/api/1.0/webhooks -H "Authorization: Bearer YOUR_TOKEN" -H "Content-Type: application/json" -d '{"data": {"resource": "PROJECT_ID", "target": "ADDRESS", "filters": [{"resource_type": "task"}]}}' (for new comments use "filters": [{"resource_type": "story", "action": "added", "resource_subtype": "comment_added"}]). Run it within 30 minutes of setting up the trigger (or of rotating its address): Asana checks the address while the command runs and Everdeck keeps the secret it sends only in that time, so there is nothing to copy back. Make one webhook per project and trigger.

Field	What to enter
Personal access token	A secret: Everdeck saves it encrypted and never shows it again. Where to find it.

Disconnecting deletes the credentials Everdeck saved, but Everdeck can't revoke them: the key, token or password itself keeps working at Asana until you delete or rotate it there.

Your Asana OAuth app

Your OAuth app.

This way signs in with an OAuth app you create for Asana, as its steps describe: Everdeck never uses an app of its own. Register this redirect URI with your app:

https://everdeck.io/api/oauth/callback

Then save the app’s client ID and secret in Everdeck, on the connect page or under OAuth apps, and sign in.

1. Open the developer console at https://app.asana.com/0/my-apps and choose Create new app.
2. Under OAuth, add the redirect URL https://everdeck.io/api/oauth/callback.
3. Under OAuth > Permission scopes, turn on Full permissions (section endpoints do not support specific scopes yet).
4. Copy the Client ID and Client secret into the form, then approve access.
5. Optional, to start work when a task changes or someone comments: once connected, set up the Asana trigger you want on Everdeck's Intake page and copy the address it gives you. Asana makes webhooks only through its API: the Asana user who signed in creates one for each project with a personal access token (developer console > Personal access tokens), as the Personal access token way of connecting describes. Make it within 30 minutes of setting up the trigger (or of rotating its address): Everdeck keeps the secret Asana sends while the webhook is made only in that time, so there is nothing to copy back.

The scopes Everdeck asks for:

• default

When you disconnect, Everdeck asks Asana to revoke the sign-in, then deletes the tokens it saved.

What agents can do

An agent uses an action only when its charter grants it, on the agent’s Tools tab, where you choose whether each one runs by itself (Auto), asks first or never runs. Each action has a risk tier: tier 3 actions, which customers or the public see, ask first unless you choose otherwise, and tier 4 actions (money, deleting things, access) always need a person. How tools and tiers work.

Actions marked Reads outside content return things people outside your company may have written. Agents treat what they read as information, never as instructions, and their riskier actions later in the same session need approval.

• List workspacesTier 0 · ReadReads outside contentasana_list_workspaces

  List the workspaces and organizations this account belongs to, with their gids.

• List projectsTier 0 · ReadReads outside contentasana_list_projects

  List projects in a workspace, with owner, due date and link.

• List sectionsTier 0 · ReadReads outside contentasana_list_sections

  List the sections (board columns) of a project. Use a section gid with move_task_to_section.

• List tasksTier 0 · ReadReads outside contentasana_list_tasks

  List tasks in a project or section, or a person's tasks in a workspace (give assignee and workspace_gid together). completed_since "now" returns only incomplete tasks. modified_since returns tasks changed after a time.

• Search tasksTier 0 · ReadReads outside contentasana_search_tasks

  Search a workspace's tasks by text and filters, most recently modified first. Needs a paid Asana plan (returns 402 on free workspaces; use list_tasks there). New changes take 10 to 60 seconds to become searchable.

• Read a taskTier 0 · ReadReads outside contentasana_get_task

  Read one task: name, description, status, assignee, dates, projects and sections, tags, parent, custom fields and link.

• Read commentsTier 0 · ReadReads outside contentasana_list_comments

  Read the comments on a task, newest first.

• Find peopleTier 0 · ReadReads outside contentasana_find_users

  Find people in a workspace by name. Returns gids to use as assignee.

• Create a taskTier 2 · ReversibleReads outside contentasana_create_task

  Create a task in one or more projects (or in a workspace with no project). Add it to a board column afterwards with move_task_to_section.

• Update a taskTier 2 · ReversibleReads outside contentasana_update_task

  Change a task's name, description, assignee, dates or custom fields, or mark it complete (completed true) or incomplete again. Send only what changes; null clears a value.

• Move a task to a sectionTier 2 · ReversibleReads outside contentasana_move_task_to_section

  Move a task into a section (board column) of a project it belongs to. It leaves its other section in that project.

• Comment on a taskTier 2 · Reversibleasana_add_comment

  Add a comment to a task. Followers of the task (including guests, if any) see it and are notified.

What can start work

These events from Asana can become tasks for your agents through Intake. How Intake works.

A task in a watched project was added, changed, completed, moved or removed.

Connect Asana first. Then, on the Intake page, open Webhooks and sources, find the connection under Connections without an address yet and select Get its URL. Give that address to Asana as the setup steps above describe: Everdeck shows it only once. Then, on the Rules tab, select New rule to say which requests become tasks and who gets them.

A comment was added to a task in a watched project (story added, subtype comment_added).

Connect Asana first. Then, on the Intake page, open Webhooks and sources, find the connection under Connections without an address yet and select Get its URL. Give that address to Asana as the setup steps above describe: Everdeck shows it only once. Then, on the Rules tab, select New rule to say which requests become tasks and who gets them.

Testing, problems and disconnecting

Everdeck checks the connection when you save it. On the connection’s page in Integrations, Test checks it again at any time.

If Asana later refuses the connection, for example because a key was deleted or a sign-in expired, the connection shows Needs attention on the Integrations page and the people who manage connections are told. Agents can’t use it until a company admin fixes it with Edit or Reconnect.

To stop agents using Asana, open the connection and select Disconnect. Agents stop using it at once and its saved credentials are deleted. What else happens depends on how it was connected: each way above says.