asana-automation
starsforks
How to install asana-automation?
samarthakv29/antigravity-god-mode/asana-automation
$npx -y skills add SamarthaKV29/antigravity-god-mode --skill asana-automationAutomate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
SKILL.md
| 1 | # Asana Automation via Rube MCP |
| 2 | |
| 3 | Automate Asana operations through Composio's Asana toolkit via Rube MCP. |
| 4 | |
| 5 | ## Prerequisites |
| 6 | |
| 7 | - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) |
| 8 | - Active Asana connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `asana` |
| 9 | - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas |
| 10 | |
| 11 | ## Setup |
| 12 | |
| 13 | **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. |
| 14 | |
| 15 | |
| 16 | 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds |
| 17 | 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `asana` |
| 18 | 3. If connection is not ACTIVE, follow the returned auth link to complete Asana OAuth |
| 19 | 4. Confirm connection status shows ACTIVE before running any workflows |
| 20 | |
| 21 | ## Core Workflows |
| 22 | |
| 23 | ### 1. Manage Tasks |
| 24 | |
| 25 | **When to use**: User wants to create, search, list, or organize tasks |
| 26 | |
| 27 | **Tool sequence**: |
| 28 | 1. `ASANA_GET_MULTIPLE_WORKSPACES` - Get workspace ID [Prerequisite] |
| 29 | 2. `ASANA_SEARCH_TASKS_IN_WORKSPACE` - Search tasks [Optional] |
| 30 | 3. `ASANA_GET_TASKS_FROM_A_PROJECT` - List project tasks [Optional] |
| 31 | 4. `ASANA_CREATE_A_TASK` - Create a new task [Optional] |
| 32 | 5. `ASANA_GET_A_TASK` - Get task details [Optional] |
| 33 | 6. `ASANA_CREATE_SUBTASK` - Create a subtask [Optional] |
| 34 | 7. `ASANA_GET_TASK_SUBTASKS` - List subtasks [Optional] |
| 35 | |
| 36 | **Key parameters**: |
| 37 | - `workspace`: Workspace GID (required for search/creation) |
| 38 | - `projects`: Array of project GIDs to add task to |
| 39 | - `name`: Task name |
| 40 | - `notes`: Task description |
| 41 | - `assignee`: Assignee (user GID or email) |
| 42 | - `due_on`: Due date (YYYY-MM-DD) |
| 43 | |
| 44 | **Pitfalls**: |
| 45 | - Workspace GID is required for most operations; get it first |
| 46 | - Task GIDs are returned as strings, not integers |
| 47 | - Search is workspace-scoped, not project-scoped |
| 48 | |
| 49 | ### 2. Manage Projects and Sections |
| 50 | |
| 51 | **When to use**: User wants to create projects, manage sections, or organize tasks |
| 52 | |
| 53 | **Tool sequence**: |
| 54 | 1. `ASANA_GET_WORKSPACE_PROJECTS` - List workspace projects [Optional] |
| 55 | 2. `ASANA_GET_A_PROJECT` - Get project details [Optional] |
| 56 | 3. `ASANA_CREATE_A_PROJECT` - Create a new project [Optional] |
| 57 | 4. `ASANA_GET_SECTIONS_IN_PROJECT` - List sections [Optional] |
| 58 | 5. `ASANA_CREATE_SECTION_IN_PROJECT` - Create a new section [Optional] |
| 59 | 6. `ASANA_ADD_TASK_TO_SECTION` - Move task to section [Optional] |
| 60 | 7. `ASANA_GET_TASKS_FROM_A_SECTION` - List tasks in section [Optional] |
| 61 | |
| 62 | **Key parameters**: |
| 63 | - `project_gid`: Project GID |
| 64 | - `name`: Project or section name |
| 65 | - `workspace`: Workspace GID for creation |
| 66 | - `task`: Task GID for section assignment |
| 67 | - `section`: Section GID |
| 68 | |
| 69 | **Pitfalls**: |
| 70 | - Projects belong to workspaces; workspace GID is needed for creation |
| 71 | - Sections are ordered within a project |
| 72 | - DUPLICATE_PROJECT creates a copy with optional task inclusion |
| 73 | |
| 74 | ### 3. Manage Teams and Users |
| 75 | |
| 76 | **When to use**: User wants to list teams, team members, or workspace users |
| 77 | |
| 78 | **Tool sequence**: |
| 79 | 1. `ASANA_GET_TEAMS_IN_WORKSPACE` - List workspace teams [Optional] |
| 80 | 2. `ASANA_GET_USERS_FOR_TEAM` - List team members [Optional] |
| 81 | 3. `ASANA_GET_USERS_FOR_WORKSPACE` - List all workspace users [Optional] |
| 82 | 4. `ASANA_GET_CURRENT_USER` - Get authenticated user [Optional] |
| 83 | 5. `ASANA_GET_MULTIPLE_USERS` - Get multiple user details [Optional] |
| 84 | |
| 85 | **Key parameters**: |
| 86 | - `workspace_gid`: Workspace GID |
| 87 | - `team_gid`: Team GID |
| 88 | |
| 89 | **Pitfalls**: |
| 90 | - Users are workspace-scoped |
| 91 | - Team membership requires the team GID |
| 92 | |
| 93 | ### 4. Parallel Operations |
| 94 | |
| 95 | **When to use**: User needs to perform bulk operations efficiently |
| 96 | |
| 97 | **Tool sequence**: |
| 98 | 1. `ASANA_SUBMIT_PARALLEL_REQUESTS` - Execute multiple API calls in parallel [Required] |
| 99 | |
| 100 | **Key parameters**: |
| 101 | - `actions`: Array of action objects with method, path, and data |
| 102 | |
| 103 | **Pitfalls**: |
| 104 | - Each action must be a valid Asana API call |
| 105 | - Failed individual requests do not roll back successful ones |
| 106 | |
| 107 | ## Common Patterns |
| 108 | |
| 109 | ### ID Resolution |
| 110 | |
| 111 | **Workspace name -> GID**: |
| 112 | ``` |
| 113 | 1. Call ASANA_GET_MULTIPLE_WORKSPACES |
| 114 | 2. Find workspace by name |
| 115 | 3. Extract gid field |
| 116 | ``` |
| 117 | |
| 118 | **Project name -> GID**: |
| 119 | ``` |
| 120 | 1. Call ASANA_GET_WORKSPACE_PROJECTS with workspace GID |
| 121 | 2. Find project by name |
| 122 | 3. Extract gid field |
| 123 | ``` |
| 124 | |
| 125 | ### Pagination |
| 126 | |
| 127 | - Asana uses cursor-based pagination with `offset` parameter |
| 128 | - Check for `next_page` in response |
| 129 | - Pass `offset` from `next_page.offset` for next request |
| 130 | |
| 131 | ## Known Pitfalls |
| 132 | |
| 133 | **GID Format**: |
| 134 | - All Asana IDs are strings (GIDs), not integers |
| 135 | - GIDs are globally unique identifiers |
| 136 | |
| 137 | **Workspace Scoping**: |
| 138 | - Most operations require a workspace context |
| 139 | - Tasks, projects, and users are workspace-scoped |
| 140 | |
| 141 | ## Quick Reference |
| 142 | |
| 143 | | Task | Tool Slug | Key Params | |
| 144 | |------|-----------|------------| |
| 145 | | List workspaces | ASANA_GET_MULTIPLE_WORKSPACES | (none) | |
| 146 | | Search tasks | ASANA_SEARCH_TASKS_IN_WORKSPACE | workspace, text | |
| 147 | | Create task | ASANA_CREATE_A_TASK | workspace, name, projects | |
| 148 | | Get task | |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
