Work anytime, anywhere with Asana. Keep remote and distributed teams, and your entire organization, focused on their goals, projects, and tasks with Asana.
23 actions Leo can use in the apps and agents it builds for you: 15 that read Asana data, 8 that create or update it.
Return list of projects given the user and workspace gid.
Docs ↗Searches for a Task by name within a Project.
Docs ↗Searches for a task by name, assignee, section, project, completed since, and modified since. Requires a Premium Asana account.
Docs ↗Searches for a section by name within a particular project.
Docs ↗Finds an existing project.
Docs ↗List workspaces available to the authenticated Asana account. Use this when you need a workspace GID before running List Teams or other workspace-scoped actions. optFields can include optional workspace properties such as email_domains and is_organization; leave offset empty for the first page and pass a returned offset token (for example, 3:0:abcdef123456) to fetch the next page.
Retrieves all users in a specified Asana workspace. Use this action to populate assignee choices for tasks, verify workspace membership, or audit user access. Requires a workspace GID, which you can obtain from the List Workspaces action. The authenticated user must have access to the workspace. Results are paginated; use the returned offset token to fetch additional pages. To include optional fields like email or photo, specify them in Opt Fields. Consider following up with Create Task or Update Task to assign work to the retrieved users.
Docs ↗Retrieves all teams in a specified Asana workspace. Use this action to discover available teams for creating projects, adding team members, or organizing work by department. Requires a workspace GID, which you can obtain from the List Workspaces action. The authenticated user must have access to the workspace; only teams visible to the user are returned. Results are paginated (default 25, max 100 per page); use the returned offset token to fetch additional pages. To include optional fields like description, visibility, or access levels, specify them in Opt Fields. Consider following up with Create Project to create a project under a team, or List Users to find team members.
Docs ↗List stories (including comments) for a task.
Docs ↗Returns a list of portfolios in the given workspace owned by the given user. Use this to discover portfolio GIDs before calling Get Portfolio or List Portfolio Items. Owner defaults to the authenticated user; regular API users can only list portfolios they own.
Docs ↗Returns a list of the items (projects) in the given portfolio. Use this after List Portfolios to answer count, timing, and spend questions; the default Opt Fields include created_at, start_on, due_on, and custom_fields. Archived filtering happens client-side because Asana has no server-side filter on this endpoint.
Retrieves available options for the Organizations field.
Returns tasks from the user's personal My Tasks inbox — NOT a project task list. Use this when the user asks for 'my tasks', 'my task list', or 'My Tasks'. Only a workspace GID is needed; no project GID required.
Docs ↗Returns the complete portfolio record for a single portfolio. Use this after List Portfolios to retrieve full portfolio details including custom fields, members, and owner; the optFields prop requests specific properties (e.g. custom_field_settings, members, start_on, due_on).
Searches for a task by id. Returns the complete task record for a single task.
Docs ↗Updates a specific and existing task.
Docs ↗Deletes a specific and existing task.
Docs ↗Creates a new task.
Docs ↗Creates a new task from a task template.
Docs ↗Adds a comment to a task.
Docs ↗Creates a new subtask and adds it to the parent task.
Docs ↗Create a new project in a workspace or team.
Docs ↗Add a task to a specific, existing section. This will remove the task from other sections of the project.
Docs ↗Leo connects Asana to the ERP your business already runs on: the records it reads in Asana land in your ERP, and what changes in the ERP flows back.
Authorize Asana once, in a couple of clicks. Leo only gets the permissions you grant.
In plain language: the dashboard, portal or agent you want across Asana and your ERP. No code, no mapping spreadsheets.
Leo builds it, you review, it goes live. Agents run on a schedule or on events, under the guardrails you set.