Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

Overview

This node integrates with Pipefy's API to create a relation between two cards. It is useful when you want to link cards in Pipefy, either by using a predefined pipe relation or by connecting cards through a specific field relation. This can help organize workflows where cards are related hierarchically or contextually.

Practical examples:

  • Linking a parent card to multiple child cards to represent subtasks or dependencies.
  • Creating relations based on custom fields that connect cards across different pipes or phases.

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. You find this ID in the card's 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).
💡 Recommendation Notice shown only if "Field Relation" is selected, recommending to use "Update fields" instead because Pipefy will not fill the field automatically when creating the relation this way.
Pipe Relation Name or ID When "Pipe Relation" is selected, choose the pipe relation ID from the list or specify it via expression. This identifies the relation defined in the card's pipe.
Phase Name or ID When "Field Relation" is selected, select the phase ID where the relation field exists. Can be chosen from a list or specified via expression.
Field Relation Name or ID When "Field Relation" is selected, select the ID of the connector-type field used for the relation. Can be chosen from a list or specified via expression.
Child ID The ID of the child card in the relation. Also found in the card's URL.

Output

The node outputs a JSON array containing the result of the relation creation operation. The exact structure depends on the Pipefy API response but generally includes confirmation of the created relation and relevant metadata.

No binary data output is involved.

Dependencies

  • Requires access to the Pipefy GraphQL API.
  • Requires an API key credential, either a service account or a personal access token.
  • The node uses dynamic loading of options for pipe relations, phases, and fields, which requires proper API permissions and connectivity.

Troubleshooting

  • Common issues:
    • Invalid or missing card IDs: Ensure the parent and child card IDs are correct and accessible.
    • Permission errors: Verify that the API credentials have sufficient rights to create relations.
    • Selecting "Field Relation" may create the relation but not update the field value; consider using the recommended "Update fields" operation instead.
  • Error messages:
    • Errors related to invalid relation IDs or missing required fields usually indicate misconfiguration of input properties.
    • Authentication failures suggest incorrect or expired API keys.

Links and References

Discussion