Pipefy
Manage pipes, cards, phases and database tables in Pipefy over Pipefy's GraphQL API.
About
Pipefy ships in the w6w first-party pack. It declares 29 actions, 1 health check, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.pipefy- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Project Management · Productivity
Overview
Pipefy’s no-code process automation platform, reached entirely through a single GraphQL endpoint — there is no REST surface at all. This app covers the spine a workflow author actually reaches for: organizations (list, get), pipes (list, get, create, update, delete), phases (list, get, create, update, delete), cards (list, get, find by field value, create, update, update a single field, move to a different phase, delete), and Database Tables (list, get, plus records: list, get, create, update, delete). An escape-hatch action runs any GraphQL query or mutation directly, reaching the much larger schema (labels, pipe members, table members, reports, webhooks, AI automations) that the named actions don’t model.
Good for creating a card whenever a form is submitted elsewhere, syncing a Pipefy Database Table with an external system of record, moving a card through approval phases from an external trigger, or pulling pipe/card data into a report.
Build with Pipefy
Three routes to the same 29 actions. The Workflow tab is generated from Pipefy's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Run GraphQL Query
graphql-query Send an arbitrary query or mutation to Pipefy's GraphQL API. Returns `data`.
Create Pipe
pipe-create Create a pipe in an organization. Set everything else with a follow-up update.
Create Table Record
table-record-create Create a record in a Database Table, optionally filling in field values.
Get Table Record
table-record-get Get a single Database Table record by ID, including its field values.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Pipefy's real ids.
{
"manifestVersion": "2",
"name": "pipefy-example",
"steps": [
{
"id": "card-create",
"uses": {
"app": "io.w6w.pipefy",
"action": "card-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"pipeId": "<pipeId>",
"title": "<title>"
}
}
]
}Here are some of the things you can do
-
Create Card
performcard-create -
Find Cards by Field Value
searchcard-find -
Get Card
readcard-get -
List Cards
searchcard-list -
Move Card to Phase
performcard-move
+24 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Pipefy, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Pipefy. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "card-create",
payload: {
pipeId: "<value>",
title: "<value>",
// fields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action card-create --payload '{"pipeId":"<value>","title":"<value>"}'Give an AI agent Pipefy — without giving it Pipefy's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.pipefy#card-create",
"input": {
"pipeId": "<pipeId>",
"title": "<title>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Pipefy connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Pipefy's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Pipefy itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Pipefy declares its own checks, so its health is a property of the app rather than something the host guesses at.
Pipefy API status
Atlassian Statuspage rollup for status.pipefy.com, anchored on the 'API (GraphQL)' component rather than the page-level rollup. Unauthenticated and unsigned.