Asana Automation via Rube MCP
Automate Asana operations through Composio's Asana toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Asana connection via
RUBE_MANAGE_CONNECTIONS with toolkit asana
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit asana
- If connection is not ACTIVE, follow the returned auth link to complete Asana OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage Tasks
When to use: User wants to create, search, list, or organize tasks
Tool sequence:
ASANA_GET_MULTIPLE_WORKSPACES - Get workspace ID [Prerequisite]ASANA_SEARCH_TASKS_IN_WORKSPACE - Search tasks [Optional]ASANA_GET_TASKS_FROM_A_PROJECT - List project tasks [Optional]ASANA_CREATE_A_TASK - Create a new task [Optional]ASANA_GET_A_TASK - Get task details [Optional]ASANA_CREATE_SUBTASK - Create a subtask [Optional]ASANA_GET_TASK_SUBTASKS - List subtasks [Optional]
Key parameters:
workspace: Workspace GID (required for search/creation)projects: Array of project GIDs to add task toname: Task namenotes: Task descriptionassignee: Assignee (user GID or email)due_on: Due date (YYYY-MM-DD)
Pitfalls:
- Workspace GID is required for most operations; get it first
- Task GIDs are returned as strings, not integers
- Search is workspace-scoped, not project-scoped
2. Manage Projects and Sections
When to use: User wants to create projects, manage sections, or organize tasks
Tool sequence:
ASANA_GET_WORKSPACE_PROJECTS - List workspace projects [Optional]ASANA_GET_A_PROJECT - Get project details [Optional]ASANA_CREATE_A_PROJECT - Create a new project [Optional]ASANA_GET_SECTIONS_IN_PROJECT - List sections [Optional]ASANA_CREATE_SECTION_IN_PROJECT - Create a new section [Optional]ASANA_ADD_TASK_TO_SECTION - Move task to section [Optional]ASANA_GET_TASKS_FROM_A_SECTION - List tasks in section [Optional]
Key parameters:
project_gid: Project GIDname: Project or section nameworkspace: Workspace GID for creationtask: Task GID for section assignmentsection: Section GID
Pitfalls:
- Projects belong to workspaces; workspace GID is needed for creation
- Sections are ordered within a project
- DUPLICATE_PROJECT creates a copy with optional task inclusion
3. Manage Teams and Users
When to use: User wants to list teams, team members, or workspace users
Tool sequence:
ASANA_GET_TEAMS_IN_WORKSPACE - List workspace teams [Optional]ASANA_GET_USERS_FOR_TEAM - List team members [Optional]ASANA_GET_USERS_FOR_WORKSPACE - List all workspace users [Optional]ASANA_GET_CURRENT_USER - Get authenticated user [Optional]ASANA_GET_MULTIPLE_USERS - Get multiple user details [Optional]
Key parameters:
workspace_gid: Workspace GIDteam_gid: Team GID
Pitfalls:
- Users are workspace-scoped
- Team membership requires the team GID
4. Parallel Operations
When to use: User needs to perform bulk operations efficiently
Tool sequence:
ASANA_SUBMIT_PARALLEL_REQUESTS - Execute multiple API calls in parallel [Required]
Key parameters:
actions: Array of action objects with method, path, and data
Pitfalls:
- Each action must be a valid Asana API call
- Failed individual requests do not roll back successful ones
Common Patterns
ID Resolution
Workspace name -> GID:
1. Call ASANA_GET_MULTIPLE_WORKSPACES
2. Find workspace by name
3. Extract gid field
Project name -> GID:
1. Call ASANA_GET_WORKSPACE_PROJECTS with workspace GID
2. Find project by name
3. Extract gid field
Pagination
- Asana uses cursor-based pagination with
offset parameter
- Check for
next_page in response
- Pass
offset from next_page.offset for next request
Known Pitfalls
GID Format:
- All Asana IDs are strings (GIDs), not integers
- GIDs are globally unique identifiers
Workspace Scoping:
- Most operations require a workspace context
- Tasks, projects, and users are workspace-scoped
Quick Reference
| Task |
Tool Slug |
Key Params |
| List workspaces |
ASANA_GET_MULTIPLE_WORKSPACES |
(none) |
| Search tasks |
ASANA_SEARCH_TASKS_IN_WORKSPACE |
workspace, text |
| Create task |
ASANA_CREATE_A_TASK |
workspace, name, projects |
| Get task |
ASANA_GET_A_TASK |
task_gid |
| Create subtask |
ASANA_CREATE_SUBTASK |
parent, name |
| List subtasks |
ASANA_GET_TASK_SUBTASKS |
task_gid |
| Project tasks |
ASANA_GET_TASKS_FROM_A_PROJECT |
project_gid |
| List projects |
ASANA_GET_WORKSPACE_PROJECTS |
workspace |
| Create project |
ASANA_CREATE_A_PROJECT |
workspace, name |
| Get project |
ASANA_GET_A_PROJECT |
project_gid |
| Duplicate project |
ASANA_DUPLICATE_PROJECT |
project_gid |
| List sections |
ASANA_GET_SECTIONS_IN_PROJECT |
project_gid |
| Create section |
ASANA_CREATE_SECTION_IN_PROJECT |
project_gid, name |
| Add to section |
ASANA_ADD_TASK_TO_SECTION |
section, task |
| Section tasks |
ASANA_GET_TASKS_FROM_A_SECTION |
section_gid |
| List teams |
ASANA_GET_TEAMS_IN_WORKSPACE |
workspace_gid |
| Team members |
ASANA_GET_USERS_FOR_TEAM |
team_gid |
| Workspace users |
ASANA_GET_USERS_FOR_WORKSPACE |
workspace_gid |
| Current user |
ASANA_GET_CURRENT_USER |
(none) |
| Parallel requests |
ASANA_SUBMIT_PARALLEL_REQUESTS |
actions |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: asana-automation3description: Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.4---56# Asana Automation via Rube MCP78Automate Asana operations through Composio's Asana toolkit via Rube MCP.910## Prerequisites1112- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)13- Active Asana connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `asana`14- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas1516## Setup1718**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.1920211. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds222. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `asana`233. If connection is not ACTIVE, follow the returned auth link to complete Asana OAuth244. Confirm connection status shows ACTIVE before running any workflows2526## Core Workflows2728### 1. Manage Tasks2930**When to use**: User wants to create, search, list, or organize tasks3132**Tool sequence**:331. `ASANA_GET_MULTIPLE_WORKSPACES` - Get workspace ID [Prerequisite]342. `ASANA_SEARCH_TASKS_IN_WORKSPACE` - Search tasks [Optional]353. `ASANA_GET_TASKS_FROM_A_PROJECT` - List project tasks [Optional]364. `ASANA_CREATE_A_TASK` - Create a new task [Optional]375. `ASANA_GET_A_TASK` - Get task details [Optional]386. `ASANA_CREATE_SUBTASK` - Create a subtask [Optional]397. `ASANA_GET_TASK_SUBTASKS` - List subtasks [Optional]4041**Key parameters**:42- `workspace`: Workspace GID (required for search/creation)43- `projects`: Array of project GIDs to add task to44- `name`: Task name45- `notes`: Task description46- `assignee`: Assignee (user GID or email)47- `due_on`: Due date (YYYY-MM-DD)4849**Pitfalls**:50- Workspace GID is required for most operations; get it first51- Task GIDs are returned as strings, not integers52- Search is workspace-scoped, not project-scoped5354### 2. Manage Projects and Sections5556**When to use**: User wants to create projects, manage sections, or organize tasks5758**Tool sequence**:591. `ASANA_GET_WORKSPACE_PROJECTS` - List workspace projects [Optional]602. `ASANA_GET_A_PROJECT` - Get project details [Optional]613. `ASANA_CREATE_A_PROJECT` - Create a new project [Optional]624. `ASANA_GET_SECTIONS_IN_PROJECT` - List sections [Optional]635. `ASANA_CREATE_SECTION_IN_PROJECT` - Create a new section [Optional]646. `ASANA_ADD_TASK_TO_SECTION` - Move task to section [Optional]657. `ASANA_GET_TASKS_FROM_A_SECTION` - List tasks in section [Optional]6667**Key parameters**:68- `project_gid`: Project GID69- `name`: Project or section name70- `workspace`: Workspace GID for creation71- `task`: Task GID for section assignment72- `section`: Section GID7374**Pitfalls**:75- Projects belong to workspaces; workspace GID is needed for creation76- Sections are ordered within a project77- DUPLICATE_PROJECT creates a copy with optional task inclusion7879### 3. Manage Teams and Users8081**When to use**: User wants to list teams, team members, or workspace users8283**Tool sequence**:841. `ASANA_GET_TEAMS_IN_WORKSPACE` - List workspace teams [Optional]852. `ASANA_GET_USERS_FOR_TEAM` - List team members [Optional]863. `ASANA_GET_USERS_FOR_WORKSPACE` - List all workspace users [Optional]874. `ASANA_GET_CURRENT_USER` - Get authenticated user [Optional]885. `ASANA_GET_MULTIPLE_USERS` - Get multiple user details [Optional]8990**Key parameters**:91- `workspace_gid`: Workspace GID92- `team_gid`: Team GID9394**Pitfalls**:95- Users are workspace-scoped96- Team membership requires the team GID9798### 4. Parallel Operations99100**When to use**: User needs to perform bulk operations efficiently101102**Tool sequence**:1031. `ASANA_SUBMIT_PARALLEL_REQUESTS` - Execute multiple API calls in parallel [Required]104105**Key parameters**:106- `actions`: Array of action objects with method, path, and data107108**Pitfalls**:109- Each action must be a valid Asana API call110- Failed individual requests do not roll back successful ones111112## Common Patterns113114### ID Resolution115116**Workspace name -> GID**:117```1181. Call ASANA_GET_MULTIPLE_WORKSPACES1192. Find workspace by name1203. Extract gid field121```122123**Project name -> GID**:124```1251. Call ASANA_GET_WORKSPACE_PROJECTS with workspace GID1262. Find project by name1273. Extract gid field128```129130### Pagination131132- Asana uses cursor-based pagination with `offset` parameter133- Check for `next_page` in response134- Pass `offset` from `next_page.offset` for next request135136## Known Pitfalls137138**GID Format**:139- All Asana IDs are strings (GIDs), not integers140- GIDs are globally unique identifiers141142**Workspace Scoping**:143- Most operations require a workspace context144- Tasks, projects, and users are workspace-scoped145146## Quick Reference147148| Task | Tool Slug | Key Params |149|------|-----------|------------|150| List workspaces | ASANA_GET_MULTIPLE_WORKSPACES | (none) |151| Search tasks | ASANA_SEARCH_TASKS_IN_WORKSPACE | workspace, text |152| Create task | ASANA_CREATE_A_TASK | workspace, name, projects |153| Get task | ASANA_GET_A_TASK | task_gid |154| Create subtask | ASANA_CREATE_SUBTASK | parent, name |155| List subtasks | ASANA_GET_TASK_SUBTASKS | task_gid |156| Project tasks | ASANA_GET_TASKS_FROM_A_PROJECT | project_gid |157| List projects | ASANA_GET_WORKSPACE_PROJECTS | workspace |158| Create project | ASANA_CREATE_A_PROJECT | workspace, name |159| Get project | ASANA_GET_A_PROJECT | project_gid |160| Duplicate project | ASANA_DUPLICATE_PROJECT | project_gid |161| List sections | ASANA_GET_SECTIONS_IN_PROJECT | project_gid |162| Create section | ASANA_CREATE_SECTION_IN_PROJECT | project_gid, name |163| Add to section | ASANA_ADD_TASK_TO_SECTION | section, task |164| Section tasks | ASANA_GET_TASKS_FROM_A_SECTION | section_gid |165| List teams | ASANA_GET_TEAMS_IN_WORKSPACE | workspace_gid |166| Team members | ASANA_GET_USERS_FOR_TEAM | team_gid |167| Workspace users | ASANA_GET_USERS_FOR_WORKSPACE | workspace_gid |168| Current user | ASANA_GET_CURRENT_USER | (none) |169| Parallel requests | ASANA_SUBMIT_PARALLEL_REQUESTS | actions |170171## When to Use172This skill is applicable to execute the workflow or actions described in the overview.173174## Limitations175- Use this skill only when the task clearly matches the scope described above.176- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.177- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
humaisali