pipefy-automations

Installation
SKILL.md

Automations

Read only the reference for your active surface: MCP or CLI. The workflows below use shared operation names and arguments.

Traditional automations (if/then rules), AI automations (prompt-driven), task automations, and simulation.

For AI agents (conversational agents with behaviors), see pipefy-ai-agents.


Start state

A build request defaults to build. The build and build inactive levels apply with or without a pipefy-process-design specification. Without a specification, the request that you restated to the user is the reference for each check in this section. Automations for a process created in this conversation start on. Test each part with acceptance cards before real cards arrive.

In this section, a pipe with cards has cards that existed before this build. Acceptance cards that the build creates do not count. After the tests, delete the acceptance cards with the usual delete confirmation.

A rule that moves a card needs a connection from the source phase to the destination phase. Before you create the rule, read the connections with get_phase_allowed_move_targets. A new connection applies at once to every card in the source phase, also while the rule is off. People and other rules can then move those cards to the destination. Add only the connections that the request or the specification names. An event such as field_updated can occur in more than one phase. If the request or the specification does not say which phases are the source, ask the user which phases to connect. If the source is already defined, do not ask again. Add each missing destination with add_phase_move_targets, all destinations of one source phase in one call. Make sure that the list in the result holds each destination.

Create an automation off only in these cases:

Installs
808
GitHub Stars
54
First Seen
Jun 2, 2026