Render Workflows (BYOK) — connector documentation
- MCP endpoint:
https://byok-render-workflows.connectorbay.com/mcp - REST API:
POST https://byok-render-workflows.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-render-workflows.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Render Workflows API key, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-render-workflows.connectorbay.com/health· Tool schemas:https://byok-render-workflows.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-render-workflows · agent@connectorbay.com
What Render Workflows (BYOK) is for
Render Workflows (BYOK) lets an AI assistant read your own Render Workflows data through the Render Workflows API with a key you supply (API key). Read-only: 6 tools (list_workflows, get_workflow, list_workflow_versions, list_tasks, list_task_runs, get_task_run). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.render.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Render Workflows. Render Workflows and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Which Render workflows do I have?"
- "How is my Render workflow built and run?"
- "Is the latest version of my Render workflow ready?"
- "Which tasks does my Render workflow define?"
- "Which workflow task runs failed recently?"
- "Why did task run trn-abc123 fail?"
What it does
list_workflows: List Render Workflows with name, slug, region, runtime, repository and branch, run command and auto-deploy trigger.get_workflow: Get one Render Workflow: region, runtime, build configuration, run command and auto-deploy trigger.list_workflow_versions: List the versions of Render Workflows with status (building, ready, failed) and creation time.list_tasks: List the tasks registered by Render Workflow versions with name, workflow and version.list_task_runs: List workflow task runs with status, start and completion time, retries and parent run. Inputs and results are left out.get_task_run: Get one workflow task run: status, timing, retries, error message and attempts (statuses and times). Inputs and results are left out.
BYOK key
You bring your own Render Workflows API key (https://dashboard.render.com/settings#api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.render.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://api-docs.render.com/reference/listworkflows (the API this connector calls, with a BYOK key)
Live from the Render Workflows API (api.render.com) with a BYOK key; documentation: https://api-docs.render.com/reference/listworkflows. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Render Workflows. Render Workflows and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Render Workflows account.
Built for: Worldwide. Languages: English.