Flowise Cloud (BYOK)

Flowise Cloud (BYOK) — connector documentation

• MCP endpoint: https://byok-flowise.connectorbay.com/mcp
• REST API: POST https://byok-flowise.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-flowise.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Flowise Cloud Flowise API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-flowise.connectorbay.com/health · Tool schemas: https://byok-flowise.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-flowise · agent@connectorbay.com

What Flowise Cloud (BYOK) is for

Flowise Cloud (BYOK) lets an AI assistant read your own Flowise Cloud data through the Flowise Cloud API with a key you supply (Flowise API key). Read-only: 8 tools (list_chatflows, get_chatflow, list_assistants, list_custom_tools, get_custom_tool, list_document_stores, get_document_store, list_upsert_history). 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 cloud.flowiseai.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Flowise Cloud. Flowise Cloud 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 chatflows do I have in Flowise and which are deployed?"
• "Show the details of Flowise chatflow cf-1"
• "Which assistants are configured in my Flowise workspace?"
• "What custom tools exist in my Flowise workspace?"
• "Describe Flowise custom tool tool-1"
• "What document stores do I have in Flowise?"

What it does

• list_chatflows: List the workspace's chatflows and agent flows with name, type, category, deployed and public flags and dates (flow definitions are not returned).
• get_chatflow: Get one chatflow's name, type, category, deployed and public flags and dates by id (the flow graph is not returned).
• list_assistants: List OpenAI-style assistants configured in Flowise with name, description, model, tool types and dates (instructions are not returned).
• list_custom_tools: List custom tools defined in Flowise with name, description and dates (code and schemas are not returned).
• get_custom_tool: Get one custom tool's name, description and dates by id (code and schema are not returned).
• list_document_stores: List document stores with name, description, status and dates.
• get_document_store: Get one document store's name, description, status and dates by id.
• list_upsert_history: List the upsert (vector indexing) history of a chatflow with ids and dates, oldest first unless DESC is asked.

BYOK key

You bring your own Flowise Cloud Flowise API key (https://cloud.flowiseai.com). 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 cloud.flowiseai.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://docs.flowiseai.com/api-reference (the API this connector calls, with a BYOK key)

Live from the Flowise Cloud API (cloud.flowiseai.com) with a BYOK key; documentation: https://docs.flowiseai.com/api-reference. 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 Flowise Cloud. Flowise Cloud 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 Flowise Cloud account.

Built for: Worldwide. Languages: English.

Flowise Cloud (BYOK) — Privacy Policy

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

What Flowise Cloud (BYOK) is. Flowise Cloud (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Flowise Cloud data: Read your Flowise Cloud chatflows, agent flows, assistants, custom tools and document stores with your own Flowise API key (no prompts or flow definitions). You bring your own Flowise Cloud Flowise API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Flowise Cloud 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 cloud.flowiseai.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 Flowise Cloud 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 Flowise Cloud receives. The request we make on your behalf, including the key and the arguments, under Flowise Cloud's own terms and privacy policy. Flowise Cloud acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Flowise Cloud 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 Flowise Cloud 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. Flowise Cloud (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 Flowise Cloud at any time to end all access.

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

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

Flowise Cloud (BYOK) — Terms of Service

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

1. The Service. Flowise Cloud (BYOK) provides: Read your Flowise Cloud chatflows, agent flows, assistants, custom tools and document stores with your own Flowise API key (no prompts or flow definitions). 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 Flowise Cloud credentials and only access data you are allowed to access. Flowise Cloud's terms apply to your use of Flowise Cloud; 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 Flowise Cloud. Flowise Cloud 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 Flowise Cloud returns, lightly trimmed; it may be incomplete, delayed or changed by Flowise Cloud. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Flowise Cloud 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 Flowise Cloud'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; Flowise Cloud 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 Flowise Cloud 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 Flowise Cloud 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-flowise

Flowise Cloud (BYOK) support

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

• MCP endpoint: https://byok-flowise.connectorbay.com/mcp
• REST API: https://byok-flowise.connectorbay.com/openapi.json
• Live status: https://byok-flowise.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. Flowise Cloud (BYOK) never asks for them.