Actions17
- Attachment Actions
- Card Actions
- Webhook Actions
- Pipe Actions
- User Actions
Overview
This node operation creates a relation between two cards in Pipefy. It supports creating relations either through a pipe-defined relation or a field-defined relation on the card. This is useful for linking related cards in workflows, such as connecting a parent card to a child card to represent dependencies or hierarchical relationships. For example, you can link a project card (parent) to task cards (children) to track progress and dependencies.
Use Case Examples
- Linking a parent card to multiple child cards to represent task dependencies.
- Creating a relation between cards using a pipe relation to maintain structured workflows.
- Using a field relation to connect cards via a specific connector field in a phase.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method to use for the Pipefy API (Service Account or Personal Access Token). This determines how the node authenticates API requests. |
| Parent ID | The ID of the parent card in the relation. This is the card from which the relation originates. |
| Relation Source | Specifies whether the relation is defined by the pipe or by a field on the card. This affects how the relation is created and managed. |
| Pipe Relation Name or ID | The ID or name of the pipe relation defined in the card's pipe. Required if Relation Source is 'pipe'. |
| Phase Name or ID | The phase ID where the relation field is located. Required if Relation Source is 'field'. |
| Field Relation Name or ID | The ID of the connector field used to define the relation. Required if Relation Source is 'field'. |
| Child ID | The ID of the child card in the relation. This is the card being linked to the parent card. |
Output
JSON
relation- Details of the created relation between the parent and child cards.
Dependencies
- Requires authentication credentials for Pipefy API (either a service account API key or a personal access token).
Troubleshooting
- Ensure that the card IDs (parent and child) are correct and accessible in Pipefy; invalid IDs will cause errors.
- If using 'Field Relation', note that Pipefy will create the relation but may not fill the field automatically; consider using 'Update fields' instead as recommended.
- Authentication errors may occur if the API key or token is invalid or expired; verify credentials are correct and have necessary permissions.
Links
- Pipefy GraphQL API Documentation - Official API documentation for Pipefy, useful for understanding how relations and cards are managed programmatically.