--- name: make-automation-df9a73507168 description: "Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas." risk: unknown source: community date_added: "2026-02-27" --- # Make Automation via Rube MCP Automate Make (formerly Integromat) operations through Composio's Make toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Make connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `make` - 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. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `make` 3. If connection is not ACTIVE, follow the returned auth link to complete Make authentication 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Get Operations Data **When to use**: User wants to retrieve operation logs or usage data from Make scenarios **Tool sequence**: 1. `MAKE_GET_OPERATIONS` - Retrieve operation records [Required] **Key parameters**: - Check current schema via RUBE_SEARCH_TOOLS for available filters - May include date range, scenario ID, or status filters **Pitfalls**: - Operations data may be paginated; check for pagination tokens - Date filters must match expected format from schema - Large result sets should be filtered by date range or scenario ### 2. List Available Languages **When to use**: User wants to see supported languages for Make scenarios or interfaces **Tool sequence**: 1. `MAKE_LIST_ENUMS_LANGUAGES` - Get all supported language codes [Required] **Key parameters**: - No required parameters; returns complete language list **Pitfalls**: - Language codes follow standard locale format (e.g., 'en', 'fr', 'de') - List is static and rarely changes; cache results when possible ### 3. List Available Timezones **When to use**: User wants to see supported timezones for scheduling Make scenarios **Tool sequence**: 1. `MAKE_LIST_ENUMS_TIMEZONES` - Get all supported timezone identifiers [Required] **Key parameters**: - No required parameters; returns complete timezone list **Pitfalls**: - Timezone identifiers use IANA format (e.g., 'America/New_York', 'Europe/London') - List is static and rarely changes; cache results when possible - Use these exact timezone strings when configuring scenario schedules ### 4. Scenario Configuration Lookup **When to use**: User needs to configure scenarios with correct language and timezone values **Tool sequence**: 1. `MAKE_LIST_ENUMS_LANGUAGES` - Get valid language codes [Required] 2. `MAKE_LIST_ENUMS_TIMEZONES` - Get valid timezone identifiers [Required] **Key parameters**: - No parameters needed for either call **Pitfalls**: - Always verify language and timezone values against these enums before using in configuration - Using invalid values in scenario configuration will cause errors ## Common Patterns ### Enum Validation Before configuring any Make scenario properties that accept language or timezone: ``` 1. Call MAKE_LIST_ENUMS_LANGUAGES or MAKE_LIST_ENUMS_TIMEZONES 2. Verify the desired value exists in the returned list 3. Use the exact string value from the enum list ``` ### Operations Monitoring ``` 1. Call MAKE_GET_OPERATIONS with date range filters 2. Analyze operation counts, statuses, and error rates 3. Identify failed operations for troubleshooting ``` ### Caching Strategy for Enums Since language and timezone lists are static: ``` 1. Call MAKE_LIST_ENUMS_LANGUAGES once at workflow start 2. Store results in memory or local cache 3. Validate user inputs against cached values 4. Refresh cache only when starting a new session ``` ### Operations Analysis Workflow For scenario health monitoring: ``` 1. Call MAKE_GET_OPERATIONS with recent date range 2. Group operations by scenario ID 3. Calculate success/failure ratios per scenario 4. Identify scenarios with high error rates 5. Report findings to user or notification channel ``` ### Integration with Other Toolkits Make workflows often connect to other apps. Compose multi-tool workflows: ``` 1. Call RUBE_SEARCH_TOOLS to find tools for the target app 2. Connect required toolkits via RUBE_MANAGE_CONNECTIONS 3. Use Make operations data to understand workflow execution patterns 4. Execute equivalent workflows directly via individual app toolkits ``` ## Known Pitfalls **Limited Toolkit**: - The Make toolkit in Composio currently has limited tools (operations, languages, timezones) - For full scenario management (creating, editing, running scenarios), consider using Make's native API - Always call RUBE_SEARCH_TOOLS to check for newly available tools - The toolkit may be expanded over time; re-check periodically **Operations Data**: - Operation records may have significant volume for active accounts - Always filter by date range to avoid fetching excessive data - Operation counts relate to Make's pricing tiers and quota usage - Failed operations should be investigated; they may indicate scenario configuration issues **Response Parsing**: - Response data may be nested under `data` key - Enum lists return arrays of objects with code and label fields - Operations data includes nested metadata about scenario execution - Parse defensively with fallbacks for optional fields **Rate Limits**: - Make API has rate limits per API token - Avoid rapid repeated calls to the same endpoint - Cache enum results (languages, timezones) as they rarely change - Operations queries should use targeted date ranges **Authentication**: - Make API uses token-based authentication - Tokens may have different permission scopes - Some operations data may be restricted based on token scope - Check that the authenticated user has access to the target organization ## Quick Reference | Task | Tool Slug | Key Params | |------|-----------|------------| | Get operations | MAKE_GET_OPERATIONS | (check schema for filters) | | List languages | MAKE_LIST_ENUMS_LANGUAGES | (none) | | List timezones | MAKE_LIST_ENUMS_TIMEZONES | (none) | ## Additional Notes ### Alternative Approaches Since the Make toolkit has limited tools, consider these alternatives for common Make use cases: | Make Use Case | Alternative Approach | |--------------|---------------------| | Trigger a scenario | Use Make's native webhook or API endpoint directly | | Create a scenario | Use Make's scenario management API directly | | Schedule execution | Use RUBE_MANAGE_RECIPE_SCHEDULE with composed workflows | | Multi-app workflow | Compose individual toolkit tools via RUBE_MULTI_EXECUTE_TOOL | | Data transformation | Use RUBE_REMOTE_WORKBENCH for complex processing | ### Composing Equivalent Workflows Instead of relying solely on Make's toolkit, build equivalent automation directly: 1. Identify the apps involved in your Make scenario 2. Search for each app's tools via RUBE_SEARCH_TOOLS 3. Connect all required toolkits 4. Build the workflow step-by-step using individual app tools 5. Save as a recipe via RUBE_CREATE_UPDATE_RECIPE for reuse ## When to Use This skill is applicable to execute the workflow or actions described in the overview. --- ## AGI Framework Integration > **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)** > Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills) ### Memory-First Protocol Cache workflow configurations and automation patterns. Retrieve prior pipeline designs to avoid re-building similar flows from scratch. ```bash # Check for prior workflow/automation context before starting python3 execution/memory_manager.py auto --query "automation patterns and workflow configurations for Make Automation" ``` ### Storing Results After completing work, store workflow/automation decisions for future sessions: ```bash python3 execution/memory_manager.py store \ --content "Workflow: automated data pipeline with retry logic, dead-letter queue, and Slack alerts on failure" \ --type technical --project \ --tags make-automation workflow ``` ### Multi-Agent Collaboration Share workflow state with other agents so they can trigger, monitor, or extend the automation. ```bash python3 execution/cross_agent_context.py store \ --agent "" \ --action "Workflow automation deployed — pipeline processing 1000+ events/day with 99.9% success rate" \ --project ``` ### Playbook Engine Combine this skill with others using the Playbook Engine (`execution/workflow_engine.py`) for guided multi-step automation with progress tracking. --- Source attribution: techwavedev Original project: https://github.com/techwavedev/agi-agent-kit/blob/58f5d95434a1adc8b41a4f391d32d95311e54936/templates/skills/extended/workflow/make-automation/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2024-2026 Elton Machado (TechWaveDev) Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: techwavedev Original project: https://github.com/techwavedev/agi-agent-kit/blob/58f5d95434a1adc8b41a4f391d32d95311e54936/templates/skills/extended/workflow/make-automation/SKILL.md Attribution basis: Source repository record Fields of work: Marketing Roles: Growth Marketer, Marketing Analyst Specialties: API, Backend, Design, DevOps, Frontend, Git, Mobile Tools: Make, Rube Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 8bf848b74077b9e9c0baf8764e5e1d259d5cb60c41df8580a573ce2ac4ac61fb