Asana logo

Asana

Project ManagementAPI tokenLive

Askel connects to your customer's Asana workspace and lets your product create tasks, update project status, and react to workflow events in the project management tool their teams rely on.

What you can do

Create tasks in any project

Insert tasks with a name, notes, due date, assignee, and custom field values into any project the Personal Access Token can access.

Update task fields and status

PATCH a task's name, notes, due date, assignee, or custom field values. Mark a task complete by setting completed to true.

Move tasks between sections

Use the addProject endpoint to move a task to a specific section within a project, useful for reflecting stage transitions from your product.

Read projects and sections

Fetch the customer's projects and their sections to build a mapping UI, so your team can configure which Asana section corresponds to each state in your product.

Create subtasks

Add subtasks to a parent task using the subtasks endpoint, allowing hierarchical task breakdowns that mirror your product's item structure.

Receive webhook events

Register an Asana webhook on a project to receive notifications when tasks are created, updated, or completed, triggering downstream steps in your workflow.

Sample use case

Creating Asana tasks when a new support ticket is escalated

You sell a customer-support platform. Foxwood Analytics uses Asana to track cross-functional escalations. When a support ticket in your product is escalated to the product team, a corresponding Asana task should appear in their Product Escalations project with the ticket ID, description, and priority.

  1. 1

    Generate a Personal Access Token

    Foxwood's Asana admin navigates to the Asana developer console at app.asana.com, creates a new Personal Access Token, and pastes it into your product's settings.

  2. 2

    Discover workspace and projects

    Askel calls the workspaces and projects endpoints to list Foxwood's Asana structure. Your CS team selects Product Escalations as the target project.

  3. 3

    Map priority to custom fields

    Foxwood has a custom field called Priority on their tasks. Askel reads the field options (High, Medium, Low) and your team maps your product's severity levels to the matching options.

  4. 4

    Create the task on escalation

    When a ticket is escalated, your product triggers the Asana workflow. Askel creates a task with the ticket title as the name, the description as the notes, and the mapped priority.

  5. 5

    Write back the Asana task URL

    Askel returns the task permalink to your product, which stores it on the ticket record. Your support team can click through to the Asana task from the ticket view.

Authentication

API token

The customer's Asana user generates a Personal Access Token from the Asana developer console at app.asana.com. Askel stores the token securely and uses it for all API calls within that user's workspace. Personal Access Tokens do not expire automatically but can be revoked from the developer console at any time.

Data flow

How Askel sits between your product and the customer's system

Data flow between Customer's Asana workspace, Askel, and Your productCustomer's Asana workspaceAPI endpointAskelauth · mapping · driftYour productyour backend
TasksProjectsSectionsCustom fieldsSubtasksWebhook events

FAQ for Asana

Which Asana plans are supported?+
The Asana API is available on all plans including Basic (free). Some features such as custom fields are restricted to Premium and above. Askel surfaces a clear error if a feature requires a plan upgrade.
Can we create tasks in multiple projects at once?+
Yes. The Asana API supports multi-homing tasks across projects. Askel can call addProject for each additional project after the initial task creation.
What happens if the customer archives or deletes a project?+
Askel detects the 404 or archived state on the next API call, pauses the workflow, and notifies your team to reconfigure the target project.
How do webhooks work if a customer's Asana project changes?+
Webhooks are registered per project. If the target project changes, the old webhook continues to receive events from the original project until it is explicitly deleted and a new one registered.
Ready to ship integrations faster?customers faster?implementations faster?
Join onboarding teams delivering integrations without the engineering queue,
catching drift before it breaks, and hitting go-live dates.
Security & Compliance
ISO 27001 Certified
GDPR Compliant

© 2025 Askel.ai. All rights reserved.