Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

Overview

This node integrates with the Pipefy platform to move a card from its current phase to another specified phase within a pipe. It is useful in workflow automation scenarios where you want to programmatically update the status or stage of a task represented by a card in Pipefy. For example, when a support ticket (card) is resolved, this node can automatically move it to the "Closed" phase.

Properties

Name Meaning
Authentication Choose the authentication method: either using a Service Account or a Personal Access Token to connect to Pipefy's API.
Card ID The unique identifier of the card you want to move. This ID can be found in the card's URL on Pipefy (e.g., https://app.pipefy.com/open-cards/[ID]).
Phase Name or ID The target phase to which the card should be moved. You can select from a dynamically loaded list of phases related to the card or specify an ID via expression.

Output

The node outputs a JSON array containing the results of the move operation for each input item. Each output item corresponds to the moved card and typically includes details about the card's new state after being moved to the specified phase.

If the node supports binary data output, it would relate to attachments or files associated with the card, but this specific operation focuses on moving cards and does not handle binary data.

Dependencies

  • Requires access to the Pipefy GraphQL API.
  • Requires valid authentication credentials, either a service account or a personal access token.
  • The node depends on dynamic loading of pipe phases based on the card ID, so network connectivity and proper permissions are necessary.
  • No additional environment variables or external services beyond Pipefy API access are required.

Troubleshooting

  • Invalid Card ID: If the card ID is incorrect or the card does not exist, the node will fail to move the card. Verify the card ID from the Pipefy UI.
  • Phase Not Found: If the specified phase ID or name is invalid or not accessible, the move operation will fail. Ensure the phase exists in the pipe and that the user has permission to move cards there.
  • Authentication Errors: Using expired or invalid credentials will cause authentication failures. Check that the API key or token is valid and has sufficient permissions.
  • API Rate Limits: Excessive requests may trigger rate limiting by Pipefy. Implement retries or reduce request frequency if needed.

Links and References

Discussion