Pipefy

Overview

This node interacts with the Pipefy API to manage cards within Pipefy workflows. Specifically, the Card: Move operation allows you to move a card from its current phase to another specified phase within a pipe. This is useful for automating workflow progressions, such as moving tasks or issues through different stages of a process.

Common scenarios:

• Automatically advancing a task card to the next phase after a certain condition is met.
• Reorganizing cards by moving them to different phases based on external triggers.
• Integrating Pipefy with other systems to reflect status changes dynamically.

Example:
You have a card representing a customer support ticket in the "New" phase. When your system detects that the ticket has been assigned, you can use this node to move the card to the "In Progress" phase automatically.

Properties

Output

The output JSON contains details about the moved card, including:

• id: The unique identifier of the card.
• title: The title of the card.
• current_phase.name: The name of the phase where the card currently resides (after the move).
• updated_at: Timestamp of when the card was last updated.

This output confirms the successful move and provides updated card information.

Dependencies

• Requires an active connection to the Pipefy API via an API key credential.
• The node uses GraphQL requests to communicate with Pipefy's API endpoint (https://api.pipefy.com/graphql).
• Proper permissions are needed on the API key to move cards between phases.

Troubleshooting

• Invalid Phase ID: If the target phase ID does not exist or is incorrect, the API will return an error. Verify the phase ID before using it.
• Permission Denied: Ensure the API key used has sufficient permissions to move cards.
• Card Not Found: If the card ID is invalid or the card does not exist, the operation will fail.
• API Rate Limits: Excessive requests may be throttled by Pipefy; handle errors accordingly.
• Continue On Fail: The node supports continuing execution on failure, which can help in batch operations where some moves might fail.

Links and References

• Pipefy API Documentation
• GraphQL Basics
• n8n Documentation - Creating Custom Nodes