Reference · built on requestConnectorWork & ticket management

Asana

Tasks, projects, sections, custom fields, and stories from Asana workspaces through the Asana API and webhooks.

Request accessPricing ↗

About

Asana is a work tracking tool built on the Work Graph. A workspace, or an organization tied to a company email domain, holds teams, projects, sections, tasks, subtasks, portfolios, and goals. A task carries a single assignee, notes, followers, and custom field values inherited from its projects, and one task can be multi-homed across several projects. The API lives at https://app.asana.com/api/1.0.

Through Fibric, an operator reads tasks and their stories, then proposes a completion, a reassignment, a due date, a section move, or a comment for your approval. Approved changes are recorded with what changed, why, and how to reverse them.

This is a reference listing. It documents what Fibric would read from Asana and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Tasks with assignee, completed, due_on, notes, memberships, and custom field values through GET /tasks/{task_gid} and Get multiple tasks
  • Tasks in a project, ordered by their position, through Get tasks from a project
  • Filtered results through Search tasks in a workspace, including custom_fields.{gid}.value and is_set parameters
  • Sections in a project and a workspace's custom fields, which give the operator its stage and status vocabulary
  • Stories on a task: comments plus system activity such as assignment and project moves
  • Webhook events with added, changed, removed, deleted, and undeleted actions on tasks, projects, portfolios, goals, and teams
  • Events since a sync token through GET on a resource's /events path, 100 events per token

Proposed actions

  • Target capability: propose a task update through PUT /tasks/{task_gid}, changing only the fields named in the data block
  • Target capability: propose a comment through Create a story on a task
  • Target capability: propose a move through Add task to section, or Add a project to a task with a position
  • Target capability: propose a new task through POST /tasks in a named project or under a parent task

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Follow up on actions from a meeting

    The operator watches tasks created after a review, checks their stories for activity, and proposes a reminder comment or a new due date when a task sits untouched.

    With Action Follow-up

  • Run an onboarding checklist

    Each new hire gets a project from a template. The operator reads sections and completion, flags the overdue steps, and proposes reassignments for the owner to approve.

    With Onboarding Checklist

  • Prepare a meeting brief

    Before a standing meeting, the operator lists tasks changed since the last one, grouped by section and custom field, and drafts the agenda for the organizer.

    With Meeting Prep

  • Coordinate a move

    Move-in tasks across projects are read by section. The operator proposes date shifts when a dependent step slips and comments on the blocked task.

    With Move Coordination

Requirements

  • An Asana workspace or organization and a user, guest, or service account whose access matches what the operator should see
  • A premium workspace or premium team membership for Search tasks in a workspace; other users receive 402 Payment Required
  • An HTTPS target that completes the X-Hook-Secret handshake while the webhook creation request is still in flight
  • OAuth scopes such as tasks:read, tasks:write, stories:write, and webhooks:write when an OAuth app is used
Authentication
A Personal Access Token, an OAuth app when several users sign in, or an Enterprise tier Service Account token, sent as a Bearer token.

Limits

  • Standard limits are 150 requests per minute for free domains and 1,500 for paid; search adds a cap of 60 per minute
  • At most 50 concurrent GET requests and 15 concurrent writes; a separate cost limit applies to expensive queries
  • Search results lag changes by 10 to 60 seconds and are not stable across repeated queries
  • A webhook that cannot be delivered for 24 hours is deleted; subscriptions run 1,000 per resource and 10,000 per token

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Asana ↗

Questions and answers

Does Asana push changes, or does the connector poll?
Both. Webhooks deliver an events array for tasks, projects, portfolios, goals, and teams, with compact events rather than full records, signed with X-Hook-Signature using a SHA256 HMAC. A heartbeat arrives every eight hours. For catch-up, the connector reads the events endpoint with a sync token.
Can a task belong to more than one project?
Yes. Asana calls this multi-homing. The memberships field lists each project, and a task can be in up to 20 projects. Subtasks do not inherit their parent's projects, and no single call returns every subtask in a project.
What does a 429 response mean?
The per-minute quota, the concurrency limit, or the cost limit was hit. The response carries a Retry-After header in seconds. Rejected requests still count against the quota, so the connector waits the stated time rather than retrying at once.
Ask about Asana

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Asana through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy