Pipefy (BYOK)

Pipefy (BYOK) — connector documentation

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

What Pipefy (BYOK) is for

Pipefy (BYOK) lets an AI assistant read your own Pipefy data through the Pipefy API with a key you supply (Pipefy personal access token or service account token). Read-only: 7 tools (get_me, list_organizations, get_organization, get_pipe, get_phase, get_table, list_pipe_templates). 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 app.pipefy.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Pipefy. Pipefy 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 Pipefy user am I connected as?"
• "Which Pipefy organizations do I have and what plan are they on?"
• "Which pipes and tables are in Pipefy organization 12345?"
• "Show the phases and start form fields of Pipefy pipe 123456"
• "What fields does Pipefy phase 301234 have?"
• "What columns does Pipefy table ZtEdWh have and how many records?"

What it does

• get_me: Show the Pipefy user the token belongs to: ID, name, username, time zone and role in the current organization.
• list_organizations: List the organizations (company accounts) the user belongs to with plan name, member count, pipe count, role and creation time.
• get_organization: Get one organization with the IDs and names of its pipes and its database tables (first 50 tables). Use the IDs with get_pipe and get_table.
• get_pipe: Get one pipe (process board): description, card counts, member count, creation time, its phases, start form fields and labels. Card contents are not returned.
• get_phase: Get one phase of a pipe: description, card count, whether it is the final (done) or draft phase, lateness limit, and its fields (ID and label).
• get_table: Get one database table: description, number of records, member count, public flag and its field definitions (ID and label). Record contents are not returned.
• list_pipe_templates: List the pipe templates Pipefy offers (ID, name, icon and image), useful to see which processes can be started from a template.

BYOK key

You bring your own Pipefy Pipefy personal access token or service account token (https://app.pipefy.com/tokens). 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 app.pipefy.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://developers.pipefy.com/llms.txt (the API this connector calls, with a BYOK key)

Live from the Pipefy API (app.pipefy.com) with a BYOK key; documentation: https://developers.pipefy.com/llms.txt. 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 Pipefy. Pipefy 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 Pipefy account.

Built for: Worldwide. Languages: English.

Pipefy (BYOK) — Privacy Policy

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

What Pipefy (BYOK) is. Pipefy (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Pipefy data: Read your Pipefy organizations, pipes, phases, start form fields, labels and database tables with your own access token. You bring your own Pipefy Pipefy personal access token or service account token; the assistant sends it to us with each request.

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

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

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

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

Pipefy (BYOK) — Terms of Service

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

1. The Service. Pipefy (BYOK) provides: Read your Pipefy organizations, pipes, phases, start form fields, labels and database tables with your own access 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 Pipefy credentials and only access data you are allowed to access. Pipefy's terms apply to your use of Pipefy; 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 Pipefy. Pipefy 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 Pipefy returns, lightly trimmed; it may be incomplete, delayed or changed by Pipefy. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Pipefy 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 Pipefy'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; Pipefy 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 Pipefy 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 Pipefy 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-pipefy

Pipefy (BYOK) support

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

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