Ironclad Workflows (BYOK)

Ironclad Workflows (BYOK) — connector documentation

• MCP endpoint: https://byok-ironclad-workflows.connectorbay.com/mcp
• REST API: POST https://byok-ironclad-workflows.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-ironclad-workflows.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Ironclad Workflows Ironclad bearer access token (legacy access token from Company Settings > API, or an OAuth access token), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-ironclad-workflows.connectorbay.com/health · Tool schemas: https://byok-ironclad-workflows.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-ironclad-workflows · agent@connectorbay.com

What Ironclad Workflows (BYOK) is for

Ironclad Workflows (BYOK) lets an AI assistant read your own Ironclad Workflows data through the Ironclad Workflows API with a key you supply (Ironclad bearer access token (legacy access token from Company Settings > API, or an OAuth access token)). Read-only: 6 tools (list_workflow_schemas, get_workflow_schema, list_workflows, get_workflow, list_webhooks, get_webhook). 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 ironcladapp.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Ironclad Workflows. Ironclad 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 contract workflow templates are available in Ironclad?"
• "What fields does the Ironclad workflow template 5f3c1b2a9d8e7a0012340001 require?"
• "Which Ironclad workflows were updated recently and what step are they in?"
• "What is the status of Ironclad workflow IC-1?"
• "Are any of my Ironclad webhooks failing or disabled?"
• "Is Ironclad webhook wh_1 enabled?"

What it does

• list_workflow_schemas: List the workflow templates (launch forms) with id, name, permissions and the fields each launch form asks for.
• get_workflow_schema: Get one workflow template's launch-form fields with type, display name, whether required and the allowed options.
• list_workflows: List workflows (active by default) with title, template, step, status and dates; contract attributes, creators and assignees are not returned.
• get_workflow: Get one workflow's title, template, step, status, dates and the state of its approval and signature stages (attributes and people are not returned).
• list_webhooks: List the account's webhooks with subscribed events, status and consecutive failure count (the target URL is not returned).
• get_webhook: Get one webhook's subscribed events, status and failure counters (the target URL is not returned).

BYOK key

You bring your own Ironclad Workflows Ironclad bearer access token (legacy access token from Company Settings > API, or an OAuth access token) (https://developer.ironcladapp.com/docs/api-authentication). 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 ironcladapp.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://developer.ironcladapp.com/reference/list-all-workflows (the API this connector calls, with a BYOK key)

Live from the Ironclad Workflows API (ironcladapp.com) with a BYOK key; documentation: https://developer.ironcladapp.com/reference/list-all-workflows. 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 Ironclad Workflows. Ironclad 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 Ironclad Workflows account.

Built for: Worldwide. Languages: English.

Ironclad Workflows (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Ironclad Workflows (BYOK) is. Ironclad Workflows (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Ironclad Workflows data: Read your Ironclad workflow templates, launch-form schemas, workflow status and webhook settings with your own bearer token. You bring your own Ironclad Workflows Ironclad bearer access token (legacy access token from Company Settings > API, or an OAuth access token); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Ironclad Workflows call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to ironcladapp.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Ironclad Workflows rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Ironclad Workflows receives. The request we make on your behalf, including the key and the arguments, under Ironclad Workflows's own terms and privacy policy. Ironclad Workflows acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Ironclad Workflows gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Ironclad Workflows data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Ironclad Workflows (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Ironclad Workflows at any time to end all access.

Children. Ironclad Workflows (BYOK) is a general-audience service operated by the adult using the assistant, under Ironclad Workflows's own age rules.

Changes. We will post changes here with a new effective date.

Ironclad Workflows (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Ironclad Workflows (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Ironclad Workflows (BYOK) provides: Read your Ironclad workflow templates, launch-form schemas, workflow status and webhook settings with your own bearer token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Ironclad Workflows credentials and only access data you are allowed to access. Ironclad Workflows's terms apply to your use of Ironclad Workflows; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Ironclad Workflows. Ironclad Workflows and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Ironclad Workflows returns, lightly trimmed; it may be incomplete, delayed or changed by Ironclad Workflows. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Ironclad Workflows account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Ironclad Workflows's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Ironclad Workflows may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Ironclad Workflows key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Ironclad Workflows takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-ironclad-workflows

Ironclad Workflows (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-ironclad-workflows.connectorbay.com/mcp
• REST API: https://byok-ironclad-workflows.connectorbay.com/openapi.json
• Live status: https://byok-ironclad-workflows.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Ironclad Workflows (BYOK) never asks for them.