Pipefy

Pipefy is a process manager: a pipe is a process, its phases are the steps work moves through, a card is one run of that process, and database tables hold the reference data cards point at.

Authentication

• Service account token

Actions

Generic API request. Run any Pipefy GraphQL query or mutation on this connection, for the case where no shipped action covers it yet. Pipefy has exactly one endpoint, so the connection supplies everything but the document and its variables.

• Create cardCreate a card in a pipe, optionally filling its start-form fields in the same call.
• Create table recordCreate a record in a database table, optionally filling its fields in the same call.
• Get cardRead one card in full: its title, whether it is done, the phase it currently sits in, who it is assigned to, its attachments and every filled field value with that field's id.
• Get database tableRead one database table and its field definitions.
• Get pipeRead one pipe's configuration: its phases, the fields on the start form, the fields on each phase, and its labels.
• List cards in a pipePage through the cards of one pipe, returning each card's id, title, current phase and filled field values.
• List database tablesPage through an organization's database tables — Pipefy's stored reference data, such as suppliers, products or customers.
• List organizationsList the Pipefy organizations this connection can reach, with each one's id and name.
• List pipesList every pipe (process) inside one Pipefy organization, with each pipe's id, name and open card count.
• List table recordsPage through the records stored in one database table, returning each record's title and its field values.
• Move card to phaseDestructiveMove a card into another phase of its pipe — the headline Pipefy operation, and what advancing a process means here.
• Update cardDestructiveChange a card's own title.
• Update card field valuesDestructiveWrite several of a card's field values in one call.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.