Overview
This node enables managing Pipefy cards with various operations including creating, updating, retrieving, searching, moving between phases, and deleting cards. Specifically, the Move Phase operation allows you to move a card from its current phase to another specified phase within Pipefy.
Common scenarios for using this node include automating workflow transitions in Pipefy pipelines, such as advancing a task card to the next stage after completion or reassigning cards to different phases based on external triggers.
For example, you could use the Move Phase operation to automatically move a customer support ticket card to the "In Progress" phase when an agent starts working on it, or move a sales lead card to the "Closed Won" phase once the deal is finalized.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to be moved. |
| Destination Phase ID | The unique identifier of the phase where the card should be moved to. |
Output
The output JSON contains the updated card object after it has been moved to the new phase. This includes all relevant card details reflecting its new state in Pipefy.
Example structure (simplified):
{
"id": "string",
"title": "string",
"phaseId": "string", // Updated to destination phase ID
"pipeId": "string",
"dueDate": "string",
"assigneeIds": ["string"],
"labelIds": ["string"],
"fieldValues": [
{
"fieldId": "string",
"fieldValue": "string"
}
]
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with Pipefy's API.
- Requires an additional API key credential for the n8n Tools API used internally.
- The node depends on Pipefy's GraphQL API endpoints for card management.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing Required Fields: If either the Card ID or Destination Phase ID is not provided, the node will throw an error indicating the missing required field. Ensure both are set correctly.
- Invalid IDs: Providing invalid or non-existent Card ID or Phase ID will result in API errors. Verify IDs exist in your Pipefy account.
- API Authentication Errors: Incorrect or expired API keys will cause authentication failures. Check that credentials are valid and have appropriate permissions.
- Permission Issues: The API user must have rights to move cards between phases in the specified pipe.
- Network or API Downtime: Temporary network issues or Pipefy API downtime can cause request failures. Retry after some time if transient errors occur.