Asana

List of Asana Fields Supported by Unito

This article details all Asana task fields and custom field types that can be synced with a Unito flow

Supported Asana task fields

This list includes every supported Asana task field, a definition, and which fields can update in both directions (2-way sync), as well as whether you can use them in rules or not.

Asana Field Definition One-way Two-way Rules?
Assignee A user assigned to the task, indicating responsibility or involvement.
Attachment A file (image, document, etc.) attached to a task.    
Comment A note or discussion point added to a task.  
Completion date Date a task was completed.    
Created at The date and time when the task was first created in Asana. Useful for tracking when a task originated and for filtering tasks based on their creation time    
Created by The Asana user who initially created the task. Helps identify the task creator and can be used to assign ownership or filter tasks in a flow.    
Description The detailed text describing the task's purpose, context, or instructions.  
Due date The date by which the task is expected to be completed.  
Globally unique task identifier A unique code that identifies the task within Asana, even across different workspaces or organizations.    
Link to task A direct URL in one synced item that opens its paired Asana task.    
Project name The name of the Asana project to which the task belongs.    
Section / column The section or column within an Asana project where the task is located.
Start date The date when the task is scheduled to begin.  
Status Defines the task state: active/open, completed or archived.
Subtask Smaller tasks nested within a parent task, breaking down larger tasks into manageable steps.  
Tag Labels or keywords used to categorize and organize tasks in Asana.
Task name The title or brief description of the task.  
Task type A task, milestone, or approval.
Updated at The date and time when the task was last modified in Asana. Useful for tracking changes    

Note:  The Section/Column and Status fields may be mapped once each, or one of those fields can be mapped twice.

That means if you include the Status field twice in a single flow, you can't then also map Section/Column. This is to prevent data conflicts from occurring. 

Supported Asana custom field types

Asana Custom Field Type One-way? Two-way? Rules?
Date  
Single-select
Multi-select
Number  
People
Text  

Quick definitions for field mappings:

    • One-Way: Changes to the Asana task field will appear in the other synced field but not vice versa.
    • Two-Way: Changes to either synced field will appear in the other.
    • Rules: This task field can be used as a trigger in your rules to filter work items from syncing with Unito.