--- name: render-automation-9458bb8386f2 description: "Automate Render tasks via Rube MCP (Composio): services, deployments, projects. Always search tools first for current schemas." risk: unknown source: community date_added: "2026-02-27" --- # Render Automation via Rube MCP Automate Render cloud platform operations through Composio's Render toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Render connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `render` - 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 `render` 3. If connection is not ACTIVE, follow the returned auth link to complete Render authentication 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. List and Browse Services **When to use**: User wants to find or inspect Render services (web services, static sites, workers, cron jobs) **Tool sequence**: 1. `RENDER_LIST_SERVICES` - List all services with optional filters [Required] **Key parameters**: - `name`: Filter services by name substring - `type`: Filter by service type ('web_service', 'static_site', 'private_service', 'background_worker', 'cron_job') - `limit`: Maximum results per page (default 20, max 100) - `cursor`: Pagination cursor from previous response **Pitfalls**: - Service types must match exact enum values: 'web_service', 'static_site', 'private_service', 'background_worker', 'cron_job' - Pagination uses cursor-based approach; follow `cursor` until absent - Name filter is substring-based, not exact match - Service IDs follow the format 'srv-xxxxxxxxxxxx' - Default limit is 20; set higher for comprehensive listing ### 2. Trigger Deployments **When to use**: User wants to manually deploy or redeploy a service **Tool sequence**: 1. `RENDER_LIST_SERVICES` - Find the service to deploy [Prerequisite] 2. `RENDER_TRIGGER_DEPLOY` - Trigger a new deployment [Required] 3. `RENDER_RETRIEVE_DEPLOY` - Monitor deployment progress [Optional] **Key parameters**: - For TRIGGER_DEPLOY: - `serviceId`: Service ID to deploy (required, format: 'srv-xxxxxxxxxxxx') - `clearCache`: Set `true` to clear build cache before deploying - For RETRIEVE_DEPLOY: - `serviceId`: Service ID - `deployId`: Deploy ID from trigger response (format: 'dep-xxxxxxxxxxxx') **Pitfalls**: - `serviceId` is required; resolve via LIST_SERVICES first - Service IDs start with 'srv-' prefix - Deploy IDs start with 'dep-' prefix - `clearCache: true` forces a clean build; takes longer but resolves cache-related issues - Deployment is asynchronous; use RETRIEVE_DEPLOY to poll status - Triggering a deploy while another is in progress may queue the new one ### 3. Monitor Deployment Status **When to use**: User wants to check the progress or result of a deployment **Tool sequence**: 1. `RENDER_RETRIEVE_DEPLOY` - Get deployment details and status [Required] **Key parameters**: - `serviceId`: Service ID (required) - `deployId`: Deployment ID (required) - Response includes `status`, `createdAt`, `updatedAt`, `finishedAt`, `commit` **Pitfalls**: - Both `serviceId` and `deployId` are required - Deploy statuses include: 'created', 'build_in_progress', 'update_in_progress', 'live', 'deactivated', 'build_failed', 'update_failed', 'canceled' - 'live' indicates successful deployment - 'build_failed' or 'update_failed' indicate deployment errors - Poll at reasonable intervals (10-30 seconds) to avoid rate limits ### 4. Manage Projects **When to use**: User wants to list and organize Render projects **Tool sequence**: 1. `RENDER_LIST_PROJECTS` - List all projects [Required] **Key parameters**: - `limit`: Maximum results per page (max 100) - `cursor`: Pagination cursor from previous response **Pitfalls**: - Projects group related services together - Pagination uses cursor-based approach - Project IDs are used for organizational purposes - Not all services may be assigned to a project ## Common Patterns ### ID Resolution **Service name -> Service ID**: ``` 1. Call RENDER_LIST_SERVICES with name=service_name 2. Find service by name in results 3. Extract id (format: 'srv-xxxxxxxxxxxx') ``` **Deployment lookup**: ``` 1. Store deployId from RENDER_TRIGGER_DEPLOY response 2. Call RENDER_RETRIEVE_DEPLOY with serviceId and deployId 3. Check status for completion ``` ### Deploy and Monitor Pattern ``` 1. RENDER_LIST_SERVICES -> find service by name -> get serviceId 2. RENDER_TRIGGER_DEPLOY with serviceId -> get deployId 3. Loop: RENDER_RETRIEVE_DEPLOY with serviceId + deployId 4. Check status: 'live' = success, 'build_failed'/'update_failed' = error 5. Continue polling until terminal state reached ``` ### Pagination - Use `cursor` from response for next page - Continue until `cursor` is absent or results are empty - Both LIST_SERVICES and LIST_PROJECTS use cursor-based pagination - Set `limit` to max (100) for fewer pagination rounds ## Known Pitfalls **Service IDs**: - Always prefixed with 'srv-' (e.g., 'srv-abcd1234efgh') - Deploy IDs prefixed with 'dep-' (e.g., 'dep-d2mqkf9r0fns73bham1g') - Always resolve service names to IDs via LIST_SERVICES **Service Types**: - Must use exact enum values when filtering - Available types: web_service, static_site, private_service, background_worker, cron_job - Different service types have different deployment behaviors **Deployment Behavior**: - Deployments are asynchronous; always poll for completion - Clear cache deploys take longer but resolve stale cache issues - Failed deploys do not roll back automatically; the previous version stays live - Concurrent deploy triggers may be queued **Rate Limits**: - Render API has rate limits - Avoid rapid polling; use 10-30 second intervals - Bulk operations should be throttled **Response Parsing**: - Response data may be nested under `data` key - Timestamps use ISO 8601 format - Parse defensively with fallbacks for optional fields ## Quick Reference | Task | Tool Slug | Key Params | |------|-----------|------------| | List services | RENDER_LIST_SERVICES | name, type, limit, cursor | | Trigger deploy | RENDER_TRIGGER_DEPLOY | serviceId, clearCache | | Get deploy status | RENDER_RETRIEVE_DEPLOY | serviceId, deployId | | List projects | RENDER_LIST_PROJECTS | limit, cursor | ## 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 Render 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 render-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/render-automation/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## 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. # Dave AI resource metadata Creator / publisher: techwavedev Original project: https://github.com/techwavedev/agi-agent-kit/blob/58f5d95434a1adc8b41a4f391d32d95311e54936/templates/skills/extended/workflow/render-automation/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: Backend Developer, DevOps / SRE, Product Manager Specialties: API, Backend, Design, DevOps, Frontend, Git Tools: Render, Rube Mcp Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: eb549bcb45df8edbd3cd9d3fa4a696feab8f4b3449ba51405f8ca07541b7104b