Overview

Asana is a work management platform that lets teams organize, track, and manage tasks and projects in one place. Persona’s integration with Asana streamlines task creation and project updates by syncing identity data between Persona and Asana.

With the Asana integration, you can automatically create and update tasks, look up users and projects, and keep assignees and due dates aligned with investigation outcomes—reducing manual work and context switching for operations, risk, and support teams.

Benefits

Automated Task Management: Create and update Asana tasks based on Persona events (e.g., verification outcomes or case escalations) to kick off work instantly.

Centralized Collaboration: Keep investigation context visible in Asana with synced notes, assignees, and dates so teams can work from a single source of truth.

Faster Resolution: Eliminate manual copy/paste by mapping Persona data to Asana fields, accelerating triage and follow-up.

Flexible Workflows: Use milestones, approvals, custom fields, and subtasks to match your team’s process without leaving Persona.

Integration Features

Persona’s Asana integration enables real-time updates, powerful automation, and dynamic lookups to support end-to-end workflows. Key capabilities include:

• Create & Update Tasks: Automatically open new tasks or update existing ones (e.g., assignee, due dates, completion status) from Persona events.
• Sync Project Context: Retrieve and reference projects, teams, users, and workspaces to route tasks to the right place.
• Assign & Schedule: Set owners, due dates, start dates, and approval statuses based on Persona logic and risk signals.

Setting up the Asana integration

Prerequisites

To set up the Asana integration, ensure you have:

• Admin access to your Asana account
• Necessary API permissions to access Asana credentials

Setting up the Asana Credentials

1. In the Persona Dashboard, navigate to Integrations > Marketplace and click on Asana
2. Click on Add Credential at the top of the page
3. Enter a credential nickname and click Continue
4. When prompted, sign in to your Asana account and approve access
5. After the credential is created, click Test to confirm it’s working. You can remove or update this credential at any time.

Using the Asana integration in a workflow

1. Create a new workflow, or open an existing workflow you’d like to update
2. Add a new Action step > Integrations
3. Select the Asana integration and choose your saved Asana credentials
4. Select the operation (e.g., Create Task, Update Task, List Projects) and map Persona data to Asana fields
5. Save/publish the workflow

Asana Operations Overview

In addition to syncing field values, Persona can create and update tasks, update projects, and search users, teams, and projects using Asana’s API. These actions support seamless two-way workflows, letting teams manage investigations without switching platforms.

See below for a comprehensive list of available Workflow Action steps and possible configurations for the Asana integration.

Listing endpoints

These endpoints retrieve metadata for Asana objects (e.g. workspaces, teams, projects, users, and tasks). In particular, each Asana object’s globally unique identifier (GID) that is returned via these endpoints will be useful for the creation and update endpoints in the following sections.

• List workspaces — A workspace is the highest-level organizational unit in Asana. All projects and tasks have an associated workspace. This endpoint returns all workspaces visible to the authorized user.
• List objects — A typeahead search API that provides search for objects from a single workspace. This endpoint should be used to query for objects when creating an auto-completion/typeahead search feature.
• List teams in a workspace — Returns all teams in the workspace visible to the authorized user.
• List projects in a workspace — Returns all projects in the workspace visible to the authorized user.
• List tasks in a project — Returns all tasks within the given project, ordered by their priority within the project.
• List users — Returns the user records for all users in all workspaces and organizations accessible to the authorized user.

To learn more about Asana APIs, see their developer documentation here.

Retrieve a team

Get details about a specific team—such as name, description, and organization—to confirm you’re targeting the correct group. Helpful when automations need to differentiate across teams within a workspace. Use the “List objects” or “List teams in a workspace” endpoints to obtain the team GID.

Configuration Steps:

• Provide values for required fields:
  • Team GID

Retrieve a project

Pull detailed data for a specific project to understand status, due dates, and workspace context. This helps workflows conditionally route or annotate tasks based on the project’s properties. Use the “List objects” or “List projects in a workspace” endpoints to obtain the project GID.

Configuration Steps:

• Provide values for required fields:
  • Project GID

Update a project

Update core project attributes to reflect workflow-driven milestones or notes. This is helpful for keeping project status aligned with investigation phases managed in Persona.

Configuration Steps:

• Provide values for required fields:
  • Project GID
• Optionally add:
  • Name
  • Status Update Title
  • Due Date
  • Notes (HTML and/or plain text)

Retrieve a task

Fetch the latest details for a specific Asana task to enrich Persona with current context before taking action. Useful for mapping assignee, dates, custom fields, and project links into your workflow. Use the “List objects” or “List tasks in a project” endpoints to obtain the task GID

Configuration Steps:

• Provide values for required fields:
  • Task GID
• Optionally add:
  • Additional fields to include in the response (to surface specific task attributes)

Update a task

Update details on an existing Asana task to reflect changes in Persona (e.g., status, ownership, or dates). This keeps task state aligned with case progress and reduces manual updates.

Configuration Steps:

• Provide values for required fields:
  • Task GID
• Optionally add:
  • Name
  • Assignee (user GID)
  • Notes/Description
  • Approval Status (Pending, Approved, Rejected, Changes Requested)
  • Completed (true/false)
  • Start Date and Due Date
  • Parent Task (to re-parent as a subtask)
  • Custom Fields (map of custom field GIDs to values)

Retrieve a user

Retrieve a specific user by their Asana identifier (ID or email) to confirm assignee details or enrich case context. This is helpful when workflows need to validate an assignee before updating a task.

Configuration Steps:

• Provide values for required fields:
  • User GID (GID or email)

Create a new task

Create a new Asana task in one or more projects directly from a Persona event, with key details automatically filled in. Use this to assign owners, add notes, set dates, and apply task types (e.g., milestone or approval) so work begins immediately.

Configuration Steps:

• Provide values for required fields:
  • Task Name
  • Project(s) to add the task to (one or more project GIDs)
• Optionally add:
  • Assignee (user GID)
  • Notes/Description
  • Workspace (workspace GID)
  • Task Type (Default Task, Milestone, Approval)
  • Completed (true/false)
  • Due Date and Start Date
  • Parent Task (to create the task as a subtask)
  • Custom Type (custom type GID)
  • Custom Fields (map of custom field GIDs to values)

FAQs

What permissions are required in Asana?

You need admin access and permissions to manage tasks, projects, teams, and users in the target workspace/team. Check with your Asana admin to confirm your organization’s access requirements.

Can I create milestones, approval tasks, or subtasks?

Yes. Set the task type to Milestone or Approval when creating a task, and use Parent Task to create a subtask.

How do I select the right workspace, project, or assignee?

Use all of the listing operations to fetch GIDs. Asana APIs rely heavily on Workspace, Team, Project, User, and Task GIDs. The endpoints are often most beneficial when utilized sequentially. For example, the GIDs that are included in response of the “List workspaces” endpoint can be used in the request bodies for the other listing endpoints. Therefore, it is recommended to store the responses from the listing endpoints as variables so you can reference them throughout your Persona Workflows.