pipefy-pipes-and-cards
Pipes & Cards
Read only the reference for your active surface: MCP or CLI. The workflows below use shared operation names and arguments.
Read, create, update, and delete pipes, phases, phase fields, labels, cards, attachments, and field conditions.
Cross-cutting patterns
-
Field types for
create_phase_fieldare the API'sFieldTypeIdenum values (lower case, e.g.short_text, notSHORT_TEXT). The tool's input schema lists them. -
Phase connections. A card moves only to a phase that its current phase connects to. A move rule in an automation or an AI agent has the same limit.
create_phase, andcreate_pipewithphases, connect each new phase to the phases beside it. A new connection applies at once to every card in the source phase. Add only the connections that the user or the specification asks for, withadd_phase_move_targets. If neither names the phases to connect, ask the user. The tool keeps the current connections. It does not remove a connection. Ask a pipe admin to remove it in the Pipefy UI. The API has no atomic add. Send all new destinations of one phase in one call. If you need more than one call on the same phase, wait for each call to finish before you start the next one. Callget_phase_allowed_move_targetsbefore moves. -
Verify-after-write. After create/update, re-read with the matching get tool (
get_pipe,get_card,get_phase_fields, etc.) before reporting success. Do not treat the write response alone as proof.