[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-fdaf568d-debd-4c44-afa1-8832780ddda7":3,"$fjhmmq1ky_H-zZN6lKgJ3DNbPC1WvMbyWbKZ_UHk8Cy0":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"fdaf568d-debd-4c44-afa1-8832780ddda7","make-automation","通过Rube MCP（Composio）自动化Make（Integromat）任务：操作、枚举、语言和时区查找。始终首先搜索工具以获取当前架构。","cat_prod_automation","mod_productivity","sickn33,productivity","---\nname: make-automation\ndescription: \"Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Make Automation via Rube MCP\n\nAutomate Make (formerly Integromat) operations through Composio's Make toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Make connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `make`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `make`\n3. If connection is not ACTIVE, follow the returned auth link to complete Make authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Get Operations Data\n\n**When to use**: User wants to retrieve operation logs or usage data from Make scenarios\n\n**Tool sequence**:\n1. `MAKE_GET_OPERATIONS` - Retrieve operation records [Required]\n\n**Key parameters**:\n- Check current schema via RUBE_SEARCH_TOOLS for available filters\n- May include date range, scenario ID, or status filters\n\n**Pitfalls**:\n- Operations data may be paginated; check for pagination tokens\n- Date filters must match expected format from schema\n- Large result sets should be filtered by date range or scenario\n\n### 2. List Available Languages\n\n**When to use**: User wants to see supported languages for Make scenarios or interfaces\n\n**Tool sequence**:\n1. `MAKE_LIST_ENUMS_LANGUAGES` - Get all supported language codes [Required]\n\n**Key parameters**:\n- No required parameters; returns complete language list\n\n**Pitfalls**:\n- Language codes follow standard locale format (e.g., 'en', 'fr', 'de')\n- List is static and rarely changes; cache results when possible\n\n### 3. List Available Timezones\n\n**When to use**: User wants to see supported timezones for scheduling Make scenarios\n\n**Tool sequence**:\n1. `MAKE_LIST_ENUMS_TIMEZONES` - Get all supported timezone identifiers [Required]\n\n**Key parameters**:\n- No required parameters; returns complete timezone list\n\n**Pitfalls**:\n- Timezone identifiers use IANA format (e.g., 'America\u002FNew_York', 'Europe\u002FLondon')\n- List is static and rarely changes; cache results when possible\n- Use these exact timezone strings when configuring scenario schedules\n\n### 4. Scenario Configuration Lookup\n\n**When to use**: User needs to configure scenarios with correct language and timezone values\n\n**Tool sequence**:\n1. `MAKE_LIST_ENUMS_LANGUAGES` - Get valid language codes [Required]\n2. `MAKE_LIST_ENUMS_TIMEZONES` - Get valid timezone identifiers [Required]\n\n**Key parameters**:\n- No parameters needed for either call\n\n**Pitfalls**:\n- Always verify language and timezone values against these enums before using in configuration\n- Using invalid values in scenario configuration will cause errors\n\n## Common Patterns\n\n### Enum Validation\n\nBefore configuring any Make scenario properties that accept language or timezone:\n```\n1. Call MAKE_LIST_ENUMS_LANGUAGES or MAKE_LIST_ENUMS_TIMEZONES\n2. Verify the desired value exists in the returned list\n3. Use the exact string value from the enum list\n```\n\n### Operations Monitoring\n\n```\n1. Call MAKE_GET_OPERATIONS with date range filters\n2. Analyze operation counts, statuses, and error rates\n3. Identify failed operations for troubleshooting\n```\n\n### Caching Strategy for Enums\n\nSince language and timezone lists are static:\n```\n1. Call MAKE_LIST_ENUMS_LANGUAGES once at workflow start\n2. Store results in memory or local cache\n3. Validate user inputs against cached values\n4. Refresh cache only when starting a new session\n```\n\n### Operations Analysis Workflow\n\nFor scenario health monitoring:\n```\n1. Call MAKE_GET_OPERATIONS with recent date range\n2. Group operations by scenario ID\n3. Calculate success\u002Ffailure ratios per scenario\n4. Identify scenarios with high error rates\n5. Report findings to user or notification channel\n```\n\n### Integration with Other Toolkits\n\nMake workflows often connect to other apps. Compose multi-tool workflows:\n```\n1. Call RUBE_SEARCH_TOOLS to find tools for the target app\n2. Connect required toolkits via RUBE_MANAGE_CONNECTIONS\n3. Use Make operations data to understand workflow execution patterns\n4. Execute equivalent workflows directly via individual app toolkits\n```\n\n## Known Pitfalls\n\n**Limited Toolkit**:\n- The Make toolkit in Composio currently has limited tools (operations, languages, timezones)\n- For full scenario management (creating, editing, running scenarios), consider using Make's native API\n- Always call RUBE_SEARCH_TOOLS to check for newly available tools\n- The toolkit may be expanded over time; re-check periodically\n\n**Operations Data**:\n- Operation records may have significant volume for active accounts\n- Always filter by date range to avoid fetching excessive data\n- Operation counts relate to Make's pricing tiers and quota usage\n- Failed operations should be investigated; they may indicate scenario configuration issues\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Enum lists return arrays of objects with code and label fields\n- Operations data includes nested metadata about scenario execution\n- Parse defensively with fallbacks for optional fields\n\n**Rate Limits**:\n- Make API has rate limits per API token\n- Avoid rapid repeated calls to the same endpoint\n- Cache enum results (languages, timezones) as they rarely change\n- Operations queries should use targeted date ranges\n\n**Authentication**:\n- Make API uses token-based authentication\n- Tokens may have different permission scopes\n- Some operations data may be restricted based on token scope\n- Check that the authenticated user has access to the target organization\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Get operations | MAKE_GET_OPERATIONS | (check schema for filters) |\n| List languages | MAKE_LIST_ENUMS_LANGUAGES | (none) |\n| List timezones | MAKE_LIST_ENUMS_TIMEZONES | (none) |\n\n## Additional Notes\n\n### Alternative Approaches\n\nSince the Make toolkit has limited tools, consider these alternatives for common Make use cases:\n\n| Make Use Case | Alternative Approach |\n|--------------|---------------------|\n| Trigger a scenario | Use Make's native webhook or API endpoint directly |\n| Create a scenario | Use Make's scenario management API directly |\n| Schedule execution | Use RUBE_MANAGE_RECIPE_SCHEDULE with composed workflows |\n| Multi-app workflow | Compose individual toolkit tools via RUBE_MULTI_EXECUTE_TOOL |\n| Data transformation | Use RUBE_REMOTE_WORKBENCH for complex processing |\n\n### Composing Equivalent Workflows\n\nInstead of relying solely on Make's toolkit, build equivalent automation directly:\n1. Identify the apps involved in your Make scenario\n2. Search for each app's tools via RUBE_SEARCH_TOOLS\n3. Connect all required toolkits\n4. Build the workflow step-by-step using individual app tools\n5. Save as a recipe via RUBE_CREATE_UPDATE_RECIPE for reuse\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,180,1477,"2026-05-16 13:27:32",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"效率工具","productivity","mdi-lightning-bolt-outline","文档处理、数据分析、自动化工作流",4,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"自动化","automation","mdi-robot-outline","工作流自动化、批处理",3,101,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"fd1a3aa3-93cd-409d-b378-59215ce5cc29","1.0.0","make-automation.zip",3139,"uploads\u002Fskills\u002Ffdaf568d-debd-4c44-afa1-8832780ddda7\u002Fmake-automation.zip","4a27c3e3421ccd681ff0a2445b5c8c32ed7f1c972aeb429eef6e21cff819156c","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":7698}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]