Actions32
- Card Actions
- Organization Actions
- Pipe Actions
- Phase Actions
- Table Actions
- Table Record Actions
- User Actions
- Webhook Actions
Overview
This node interacts with the Pipefy API to manage phases within a workflow pipe. Specifically, the "Delete Phase" operation allows users to delete a phase by its unique identifier. This is useful for automating cleanup or restructuring of workflow phases in Pipefy without manual intervention.
Common scenarios include:
- Removing obsolete or completed phases from a pipe.
- Automating phase lifecycle management as part of a larger workflow.
- Integrating Pipefy phase deletion into multi-step automation processes.
Example: Automatically deleting a phase when a project is archived or no longer needed.
Properties
| Name | Meaning |
|---|---|
| Phase ID | The unique identifier of the phase to delete |
Output
The output JSON contains a single field indicating whether the deletion was successful:
{
"success": true
}
success: A boolean value that istrueif the phase was deleted successfully, otherwisefalse.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Pipefy API via an API key credential configured in n8n.
- The node sends GraphQL mutation requests to the Pipefy API endpoint at
https://api.pipefy.com/graphql. - Proper permissions on the API key are necessary to delete phases.
Troubleshooting
Common issues:
- Invalid or missing Phase ID: Ensure the Phase ID provided exists and is correct.
- Insufficient permissions: The API key must have rights to delete phases.
- Network or API errors: Check connectivity and Pipefy service status.
Error messages:
"Phase not found": The specified Phase ID does not exist."Unauthorized"or"Permission denied": The API key lacks required permissions."GraphQL error": Could indicate malformed request or server-side issues.
Resolutions:
- Verify the Phase ID input.
- Confirm API key permissions and validity.
- Retry after network checks or wait if Pipefy API is down.