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_field are the API's FieldTypeId enum values (lower case, e.g. short_text, not SHORT_TEXT). The tool's input schema lists them.

• extra_input merges extra API keys (camelCase); keys that duplicate primary arguments are ignored.

• Phase connections are UI-only. Creating or reordering phases does not wire Phase Connections / allowed_phases. Configure edges in the Pipefy UI; use get_phase_allowed_move_targets before moves. The API cannot add transition edges.

• 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.

Pipe operations