Skip to main content
Asana is a powerful project management and team collaboration platform that helps organizations manage their work, track projects, and achieve their goals. It provides a comprehensive suite of tools for task management, project tracking, team coordination, and workflow optimization.

​
Configuring Asana as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Asana option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need OAuth credentials to connect to Asana. You’ll need to provide:
  • Authorization: Log in with your Asana account and grant permissions for Nekt to access your workspace data.
  • Workspace ID: The ID of your Asana workspace. You can get it from the Admin URL (https://app.asana.com/admin/), it’s the number that appears right next to https://app.asana.com/admin/. Alternatively, if you’re logged in with your account, you can click this link and simply copy the gid value.

​
2. Select streams

Choose which data streams you want to sync - you can select all streams or pick specific ones that matter most to you. The available streams include projects, tasks, teams, portfolios, and more.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select a name for each table (which will contain the fetched data) and the type of sync.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can determine when to execute a full sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while. Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Asana and their corresponding fields:
Stream for managing projects in your Asana workspace.Key Fields:
  • gid: Unique identifier for the project
  • name: Name of the project
  • resource_type: The project type
Stream for managing tasks within projects.Key Fields:
  • gid: Unique identifier for the task
  • name: Name/title of the task
  • resource_type: The resource type (task)
  • resource_subtype: The resource subtype (e.g., default_task)
  • created_by: User who created the task (includes gid, resource_type)
  • approval_status: The approval status of the task
  • assignee_status: Status of the task for the assignee
  • completed: Whether the task is completed
  • completed_at: When the task was completed
  • completed_by: User who completed the task (includes gid, resource_type, name)
  • created_at: When the task was created
  • dependencies: Array of tasks this task depends on
  • dependents: Array of tasks that depend on this task
  • due_at: The due time for the task
  • due_on: The due date for the task
  • html_notes: Task notes in HTML format
  • notes: Task notes in plain text
  • hearted: Whether the task is hearted/favorited
  • hearts: Array of hearts on the task (includes user details)
  • is_rendered_as_separator: Whether the task is rendered as a separator
  • liked: Whether the task is liked
  • likes: Array of likes on the task (includes user details)
  • modified_at: When the task was last modified
  • num_hearts: Number of hearts on the task
  • num_likes: Number of likes on the task
  • num_subtasks: Number of subtasks
  • start_at: The start time for the task
  • start_on: The start date for the task
  • actual_time_minutes: The actual time spent on the task in minutes
  • assignee: User assigned to the task (includes gid, resource_type, name)
  • assignee_section: Section this task is assigned to (includes gid, resource_type, name)
  • custom_fields: Array of custom fields with detailed information including:
    • Basic info (gid, name, type, description)
    • Field configuration (enabled, precision, format, currency_code)
    • Values (date_value, enum_value, multi_enum_values, number_value, text_value)
    • Display settings (custom_label, custom_label_position)
    • Permissions (is_global_to_workspace, has_notifications_enabled, is_value_read_only)
  • custom_type: Custom type for this task (includes gid, resource_type, name)
  • custom_type_status_option: Custom type status option (includes gid, resource_type, name)
  • followers: Array of users following this task (includes gid, resource_type, name)
  • parent: Parent task details (includes gid, name, resource_type, created_by)
  • projects: Array of projects this task belongs to (includes gid, resource_type, name)
  • tags: Array of tags applied to this task (includes gid, resource_type, name)
  • workspace: Workspace this task belongs to (includes gid, resource_type, name)
  • permalink_url: Direct URL to the task in Asana
Stream for managing subtasks within tasks.Key Fields:
  • gid: Unique identifier for the subtask
  • task_id: Parent task ID from context
  • resource_type: The resource type (task)
  • name: Name of the subtask
  • resource_subtype: The resource subtype (e.g., default_task)
  • created_by: User who created this subtask
  • approval_status: Approval status of the subtask
  • assignee_status: Assignee status of the subtask
  • completed: Whether the subtask is completed
  • completed_at: When the subtask was completed
  • completed_by: User who completed this subtask
  • created_at: When the subtask was created
  • dependencies: Array of tasks this subtask depends on
  • dependents: Array of tasks that depend on this subtask
  • due_at: Due time for the subtask
  • due_on: Due date for the subtask
  • html_notes: Subtask notes in HTML format
  • notes: Subtask notes in plain text
  • hearted: Whether the current user hearted the subtask
  • hearts: Array of hearts on the subtask
  • is_rendered_as_separator: Whether rendered as a separator
  • liked: Whether the current user liked the subtask
  • likes: Array of likes on the subtask
  • modified_at: When the subtask was last modified
  • num_hearts: Number of hearts on the subtask
  • num_likes: Number of likes on the subtask
  • num_subtasks: Number of subtasks of this subtask
  • start_at: Start time for the subtask
  • start_on: Start date for the subtask
  • actual_time_minutes: Actual time spent in minutes
  • assignee: User assigned to this subtask
  • assignee_section: Section this subtask is assigned to
  • custom_fields: Array of custom fields with detailed information
  • custom_type: Custom type for this subtask
  • custom_type_status_option: Custom type status option
  • followers: Array of users following this subtask
  • parent: Parent task details
  • projects: Array of projects this subtask belongs to
  • tags: Array of tags applied to this subtask
  • workspace: Workspace this subtask belongs to
  • permalink_url: Direct URL to the subtask in Asana
Stream for managing teams in your workspace.Key Fields:
  • gid: Unique identifier for the team
  • name: Name of the team
  • resource_type: The resource type (team)
  • description: Team description
  • html_description: Team description in HTML format
  • organization: Organization this team belongs to (includes gid, resource_type, name)
  • visibility: Visibility of the team (public, private)
  • created_at: When this team was created
  • updated_at: When this team was last updated
  • permalink_url: Direct URL to the team in Asana
Stream for managing users in your workspace.Key Fields:
  • gid: Unique identifier for the user
  • name: User’s full name
  • resource_type: The resource type (user)
  • email: User’s email address
  • photo: User’s profile photo URLs in various sizes:
    • 21x21, 27x27, 36x36
    • 60x60, 128x128, 1024x1024
  • workspaces: Array of workspaces the user belongs to (includes gid, resource_type, name)
Stream for managing tags used to categorize tasks.Key Fields:
  • gid: Unique identifier for the tag
  • name: Name of the tag
  • resource_type: The resource type (tag)
  • color: Color assigned to the tag
  • created_at: When the tag was created
  • created_by: User who created this tag (includes gid, resource_type, name)
  • notes: Tag description/notes
  • followers: Array of users following this tag (includes gid, resource_type, name)
  • workspace: Workspace this tag belongs to (includes gid, resource_type, name)
  • permalink_url: Direct URL to the tag in Asana
Stream for tracking activity and comments on tasks.Key Fields:
  • gid: Unique identifier for the story
  • task_id: The parent task ID this story belongs to
  • resource_type: The resource type (story)
  • created_at: When the story was created
  • created_by: User who created the story (includes gid, resource_type, name)
  • resource_subtype: The resource subtype (e.g., comment_added)
  • text: The plain text of the story
  • html_text: The HTML text of the story
  • is_editable: Whether the story is editable
  • target: Target object of this story (includes gid, resource_type, name)
  • action_taken: The action taken
  • old_resource_subtype: The old resource subtype
  • new_resource_subtype: The new resource subtype
  • old_text: The old text
  • new_text: The new text
  • old_name: The old name
  • new_name: The new name
  • old_dates: Previous dates (due_on, due_at, start_on, start_at)
  • new_dates: Updated dates (due_on, due_at, start_on, start_at)
  • old_number_value: The old number value
  • new_number_value: The new number value
  • old_enum_value: Previous enum value details
  • new_enum_value: Updated enum value details
  • old_multi_enum_values: Previous multi-enum values
  • new_multi_enum_values: Updated multi-enum values
  • old_custom_field_value: Previous custom field value details
  • new_custom_field_value: Updated custom field value details
  • previews: Array of previews for this story (includes text, links, headers)
  • attachments: Array of attachments (includes metadata and URLs)
Stream for managing custom fields in your workspace.Key Fields:
  • gid: Unique identifier for the custom field
  • resource_type: The resource type (custom_field)
  • resource_subtype: The resource subtype (e.g., text, number, enum)
  • name: Name of the custom field
  • description: Description of the custom field
  • type: Type of the custom field (text, number, enum, multi_enum, date, people)
  • enum_options: Array of possible values for enum custom fields, each containing:
    • Basic info (gid, name)
    • Display settings (color, enabled)
  • enabled: Whether the custom field is enabled
  • representation_type: The representation type of the custom field
  • id_prefix: The ID prefix for the custom field
  • is_formula_field: Whether it’s a formula field
  • number_value: The number value for number custom fields
  • text_value: The text value for text custom fields
  • display_value: The display value for the custom field
  • date_value: The date value for date custom fields (date and date_time)
  • enum_value: The enum value for enum custom fields
  • multi_enum_values: Array of values for multi_enum custom fields
  • people_value: Array of users for people custom fields
  • created_by: User who created the custom field
  • precision: Number of decimal places for number fields
  • format: Format of the custom field
  • currency_code: Currency code for currency fields
  • custom_label: Custom label for the field
  • custom_label_position: Position of custom label (prefix, suffix)
  • is_global_to_workspace: Whether global to workspace
  • has_notifications_enabled: Whether notifications are enabled
  • asana_created_field: The Asana created field type
  • is_value_read_only: Whether the value is read-only
  • privacy_setting: Privacy setting for the custom field
  • default_access_level: Default access level for the custom field
Stream for managing portfolios that group related projects.Key Fields:
  • gid: Unique identifier for the portfolio
  • name: Name of the portfolio
  • resource_type: The portfolio type
  • archived: Whether the portfolio is archived
  • color: Color assigned to the portfolio
  • created_at: When the portfolio was created
  • created_by: User who created the portfolio (includes gid, resource_type, name)
  • custom_field_settings: Array of custom field settings with detailed configuration
  • current_status_update: Current status update details (includes title and type)
  • due_on: Due date for the portfolio
  • custom_fields: Array of custom fields with values and configuration
  • members: Array of users who are members of this portfolio
  • owner: Owner of this portfolio (includes gid, resource_type, name)
  • start_on: Start date for the portfolio
  • workspace: Workspace this portfolio belongs to (includes gid, resource_type, name)
  • permalink_url: Direct URL to the portfolio in Asana
  • public: Whether the portfolio is public to its team
  • default_access_level: Default access level for the portfolio
  • privacy_setting: Privacy setting for the portfolio
  • project_templates: Array of project templates associated with this portfolio
Stream for managing items within portfolios.Key Fields:
  • gid: Unique identifier for the project/item
  • resource_type: The resource type (project)
  • name: The project/item name
  • portfolio_id: The portfolio ID this item belongs to
Stream for managing custom fields specific to portfolios.Key Fields:
  • gid: Unique identifier for the custom field setting
  • resource_type: The resource type (custom_field_setting)
  • project: Project this setting belongs to (if applicable)
  • portfolio: Portfolio this setting belongs to
  • custom_field: Detailed custom field information including:
    • Basic info (gid, name, type, description)
    • Field configuration (enabled, precision, format, currency_code)
    • Display settings (custom_label, custom_label_position)
    • Values (enum_value, multi_enum_values, number_value, text_value, date_value, people_value)
    • Permissions (is_global_to_workspace, has_notifications_enabled, is_value_read_only)
  • is_important: Whether this custom field is marked as important
  • parent: Parent portfolio/project for this setting
  • created_at: When this setting was created
  • created_by: User who created this setting
  • portfolio_id: Portfolio ID this setting belongs to
Stream for managing custom fields specific to projects.Key Fields:
  • gid: Unique identifier for the custom field setting
  • resource_type: The resource type (custom_field_setting)
  • project: Project this setting belongs to
  • custom_field: Detailed custom field information including:
    • Basic info (gid, name, type, description)
    • Field configuration (enabled, precision, format, currency_code)
    • Display settings (custom_label, custom_label_position)
    • Values (enum_value, multi_enum_values, number_value, text_value, date_value, people_value)
    • Permissions (is_global_to_workspace, has_notifications_enabled, is_value_read_only)
  • is_important: Whether this custom field is marked as important
  • parent: Parent project for this setting
  • created_at: When this setting was created
  • created_by: User who created this setting
  • project_id: Project ID this setting belongs to
Stream for tracking project status updates.Key Fields:
  • gid: Unique identifier for the status update
  • project_id: The parent project ID this status belongs to
  • resource_type: The resource type (project_status)
  • title: Title of the status update
  • text: Text content of the status update
  • html_text: HTML content of the status update
  • color: Color of the status
  • created_at: When the status was created
  • created_by: User who created the status (includes gid, resource_type, name)
  • author: Author of the status (includes gid, resource_type, name)
  • modified_at: When the status was last modified
  • status_type: Type of status (on_track, at_risk, off_track, on_hold, complete)
  • liked: Whether the current user has liked this status
  • likes: Array of users who liked this status
  • num_likes: Number of likes on this status
  • hearts: Array of users who hearted this status
  • num_hearts: Number of hearts on this status
Stream for tracking time entries on tasks.Key Fields:
  • gid: Unique identifier for the time entry
  • resource_type: The resource type (time_tracking_entry)
  • created_at: When the time entry was created
  • created_by: User who created the entry (includes gid, resource_type, name)
  • completed: Whether the entry is completed
  • completed_at: When the entry was completed
  • duration_minutes: Duration of the entry in minutes
  • notes: Notes for the time entry
  • html_notes: Notes in HTML format
  • user: User who performed this time tracking
  • task: Task this entry is associated with (includes gid, resource_type, name)
  • project: Project this entry is associated with (includes gid, resource_type, name)
  • workspace: Workspace this entry belongs to (includes gid, resource_type, name)
  • time_period: Time period details including:
    • Basic info (gid, display_name)
    • Date range (start_on, end_on)
Stream for managing resource allocations.Key Fields:
  • gid: Unique identifier for the allocation
  • project_id: The project ID from context
  • resource_type: The resource type (allocation)
  • resource_subtype: The resource subtype (e.g., project_allocation)
  • start_date: Start date of the allocation period
  • end_date: End date of the allocation period
  • effort: Effort details including:
    • Type (e.g., hours)
    • Value (numeric amount)
  • assignee: User assigned to this allocation (includes gid, name, resource_type)
  • created_by: User who created this allocation (includes gid, name, resource_type)
  • parent: Parent project this allocation belongs to (includes gid, name, resource_type)
Stream for managing organizational goals.Key Fields:
  • gid: Unique identifier for the goal
  • resource_type: The resource type (goal)
  • name: Name of the goal
  • html_notes: Goal notes in HTML format
  • notes: Goal notes in plain text
  • due_on: Due date for the goal
  • start_on: Start date for the goal
  • is_workspace_level: Whether the goal is workspace-level
  • liked: Whether the current user liked the goal
  • likes: Array of likes on the goal
  • num_likes: Number of likes on the goal
  • team: Team associated with this goal (includes gid, resource_type, name)
  • workspace: Workspace this goal belongs to (includes gid, resource_type, name)
  • followers: Array of users following this goal
  • time_period: Time period details including:
    • Basic info (gid, period, display_name)
    • Date range (start_on, end_on)
  • metric: Associated metric details including:
    • Basic info (gid, type, subtype)
    • Configuration (precision, unit, currency_code)
    • Values (initial, target, current)
    • Permissions (can_manage)
  • owner: Owner of this goal (includes gid, resource_type, name)
  • current_status_update: Current status update details
  • status: Status of the goal (green, yellow, red)
⌘I