Asana

The Asana app connects Asana work management to Sprigr Team. Agents can find tasks and projects by name, read their details and comments, create and update tasks, complete, move and reparent them, add comments with @-mentions, attach files and links, create tasks from templates, post status updates, and work with sections, tags, custom fields, portfolios, goals and time tracking. A search mirror keeps task lookups fast on any Asana plan, Asana webhooks keep it current, and task changes are emitted as events workflows can act on.

Note

Asana ships as a marketplace app with one connection per install. Whoever authorises grants the install access to their Asana workspaces, and every agent with the app acts as that account: comments and edits are attributed to it. Connect with an account whose permissions match what your agents should see and do.

Prerequisites

• An Asana account with access to the workspaces and projects you want agents to use. Free and paid plans both work; the app does not depend on Asana’s paid Search API.
• Admin or Owner role in your Sprigr Team organisation to install the app.

Installing and connecting

1. Install the app

   Sign in to team.sprigr.com, open Apps in the sidebar, find Asana under Available, and install it. No secrets are requested. See Installing Apps.

2. Connect an Asana account

   Open the app’s settings page from Apps > Installed and click Connect Asana. Sign in to Asana and approve the request. The page then shows the connection, the default workspace, and the sync and webhook status.

3. Choose what to watch

   Under Watched projects, pick the projects the search mirror and real-time updates cover, or choose Whole workspace to include new projects automatically. Set the Default workspace that actions use when a request does not name one.

4. Check the connection

   Ask your agent “What is on my plate in Asana this week?” It resolves you by name and lists your tasks.

Try asking your agent

“Create a task in the Website Relaunch project called ‘Update pricing page copy’, assign it to Priya, due Friday, and mention Tom in a comment.”

“Which tasks in the Q4 Launch project are overdue, and who owns them?”

Sync, webhooks, events and undo

• Search mirror. Tasks and projects in watched projects are mirrored into a search index in your workspace, so “the invoice task” resolves to the right task by name without Asana’s paid search. The mirror is a resolver: the agent always reads the live task before acting. An incremental sync runs every 15 minutes and a full re-walk nightly, which also marks tasks deleted in Asana.
• Real-time updates. The app registers Asana webhooks for each watched project plus one for the workspace, and reconciles them nightly because Asana silently drops a webhook after repeated failed deliveries.
• Events for workflows. Changes are emitted as asana.task.created, asana.task.updated, asana.task.completed, asana.task.deleted, asana.comment.added, asana.section.changed, asana.project.created and asana.project.status_updated, which a workflow can subscribe to.
• Confirmation and approval. Sixty-one actions pause for confirmation before they run: every delete, every change to who can see or do what, everything that notifies a person, the timesheet actions, and bulk writes above five objects. Twenty-five of those go further and show an approval card a person must tap. Eight deletes are irreversible and say so on the card.
• Undo. Reversible writes are journalled, and the platform’s list_undoable_changes and undo_change tools put a change back.

What agents can do

The app exposes a single asana tool that takes an action, with 211 actions. Every object is identified by a gid; when you only have a name, find or a list_* action resolves it first. At a category level:

• Tasks: list, search, get, create (single, bulk, or from a template), update, complete and reopen, move between sections, set parent, duplicate, add and remove followers, tags and dependencies, delete.
• Comments and rich text: add comments with @-mentions by name or email, update and delete comments, reactions, status updates.
• Attachments: upload a link or a file from your Sprigr file store, list, download, delete.
• Projects and sections: list, search, get, create, update, duplicate, save as template; project briefs, members and followers; sections and their order; task counts.
• Workspaces, teams and users: workspaces, teams and memberships, users and their task lists, access requests.
• Custom fields: definitions, enum options, attaching fields to projects, portfolios and goals.
• Portfolios and goals: portfolios and their items and members; goals, metrics, relationships and progress.
• Time and resourcing: time entries, timesheets and approvals, time periods, allocations, budgets, rates, roles, out-of-office entries.
• Automation and exports: trigger rules, graph and resource exports, job polling.

Dates: a due date is a calendar date, a due time is a timestamp, and the two cannot both be set on one write.

Common use cases

• Standups. “What did the team complete yesterday and what is due today?” reads the watched projects.
• Tasks from conversations. A team member describes work in chat and the agent creates the task with the right project, assignee, due date and a comment for context.
• Status roll-ups. A weekly workflow posts a status update on each active project from its completed and overdue tasks.
• Cross-system links. A workflow on asana.task.completed closes the matching ticket or notifies the customer.
• Time tracking. The agent logs time entries and lists what is awaiting timesheet approval.

Troubleshooting

Not connected Nobody has completed the Connect Asana step, or the connection was revoked. Reconnect from the settings page under Connection.

A task the agent cannot find Search covers watched projects only. Add the project under Watched projects, or ask the agent to list the project’s tasks directly.

“Paid plan feature” errors Some Asana features (portfolios, goals, custom fields, time tracking) need a paid Asana plan. The error names the feature; the app does not retry.

An action is waiting for confirmation or approval Deletes, permission changes and anything that notifies people pause until you confirm, or tap the approval card, in the chat.

Real-time updates stopped Asana removes a webhook after failed deliveries. The nightly check re-registers it; the settings page shows the last webhook check and any failure.

Next steps

• Integrations Overview: See all available integrations.
• Workflows: React to Asana task and project events.
• Decisions and approvals: How approval cards work.