Actions32
- Card Actions
- Organization Actions
- Pipe Actions
- Phase Actions
- Table Actions
- Table Record Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy API to manage "pipes," which are workflows or process containers in Pipefy. Specifically, the Delete Pipe operation allows users to delete an existing pipe by its ID. This is useful for automating cleanup tasks, managing workflow lifecycle, or removing obsolete processes programmatically.
Common scenarios:
- Automatically deleting pipes that are no longer needed after a project completes.
- Cleaning up test or temporary pipes created during automated testing.
- Managing organizational resources by removing unused pipes via automation.
Example usage:
- A workflow triggers when a project status changes to "archived" and deletes the associated pipe in Pipefy using this node.
- Scheduled automation that deletes pipes older than a certain date to keep the workspace tidy.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | The unique identifier of the pipe to delete |
Output
The output JSON contains a single field indicating whether the deletion was successful:
{
"success": true
}
success: A boolean value indicating if the pipe was deleted successfully (true) or not (false).
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 requests to
https://api.pipefy.com/graphql. - Proper permissions on the API key are necessary to delete pipes.
Troubleshooting
Common issues:
- Invalid or missing Pipe ID: Ensure the Pipe ID provided is correct and exists.
- Insufficient permissions: The API key must have rights to delete pipes.
- Network or API errors: Check connectivity and Pipefy service status.
Error messages:
"An unknown error occurred": Generic catch-all; check detailed error logs.- API errors returned from Pipefy (e.g., permission denied, pipe not found) will be included in the error message.
Resolution tips:
- Verify the Pipe ID is accurate.
- Confirm API credentials have delete permissions.
- Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.