Pipefy icon

Pipefy

Interact with Pipefy GraphQL API

Actions17

Overview

This node integrates with Pipefy's API to create a relation between two cards. It supports creating relations either via a pipe-defined relation or a field-defined relation on the card. This is useful for automating workflows where cards need to be linked, such as connecting a parent task card to subtasks or associating related requests.

Practical examples:

  • Automatically linking a newly created subtask card to its parent task card.
  • Creating relations between cards based on business logic, e.g., connecting a customer support ticket card to a billing issue card.

Properties

Name Meaning
Authentication Choose the authentication method: "Service Account" or "Personal Access Token".
Parent ID The ID of the parent card in the relation. Must be exactly 10 characters. Found in the card URL (e.g., https://app.pipefy.com/open-cards/[ID]).
Relation Source Select how the relation is defined: "Pipe Relation" (relation defined in the card's pipe) or "Field Relation" (relation defined in a field of the card).
Pipe Relation Name or ID When using "Pipe Relation" source, select or specify the pipe relation ID defined in the card's pipe.
Phase Name or ID When using "Field Relation" source, select the phase ID where the relation field exists.
Field Relation Name or ID When using "Field Relation" source, select the ID of the connector-type field that defines the relation.
Child ID The ID of the child card in the relation. Must be exactly 10 characters. Found in the card URL (e.g., https://app.pipefy.com/open-cards/[ID]).

Note: When using "Field Relation", there is a recommendation to use "Update fields" instead because while the relation will be created, Pipefy will not fill the field automatically.

Output

The node outputs an array of JSON objects representing the result of the relation creation operation. Each object corresponds to one execution item and contains the response from Pipefy's API about the created relation.

If binary data were involved, it would be summarized here, but this node deals only with JSON data related to card relations.

Dependencies

  • Requires access to Pipefy's GraphQL API.
  • Requires either a service account API credential or a personal access token credential configured in n8n.
  • The node uses dynamic option loading methods to fetch pipe relations, phases, and fields based on user input.

Troubleshooting

  • Invalid Card IDs: Ensure that both Parent ID and Child ID are exactly 10 characters long and correspond to valid card IDs visible in the Pipefy UI URL.
  • Relation Not Created: If using "Field Relation" source, note that Pipefy does not auto-fill the field; consider using the "Update fields" operation instead.
  • Authentication Errors: Verify that the selected authentication method has valid credentials and sufficient permissions.
  • Missing Options: Dynamic loading of pipe relations, phases, or fields depends on correct Parent ID and relation source selection. Make sure these inputs are correctly set to load options properly.

Links and References

Discussion