Actions11
Overview
This node enables managing Pipefy pipes through various operations such as creating, updating, retrieving, deleting pipes, and managing pipe members and phases. Specifically, the Delete operation removes a pipe identified by its ID from Pipefy.
Common scenarios for using this node include automating workflow management in Pipefy, such as cleaning up obsolete pipes, integrating pipe lifecycle management into broader automation workflows, or synchronizing Pipefy data with other systems.
For example, you might use the Delete operation to automatically remove pipes that are no longer needed after a project completes, helping maintain an organized Pipefy environment without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | The unique identifier of the pipe to delete. This is required to specify which pipe should be removed. |
Output
The output JSON object contains the following fields:
success(boolean): Indicates whether the deletion was successful.pipeId(string): The ID of the pipe that was requested to be deleted.message(string): A human-readable message indicating the result, e.g., "Pipe deleted successfully" or "Failed to delete pipe".
No binary data is output by this operation.
Example output:
{
"success": true,
"pipeId": "12345",
"message": "Pipe deleted successfully"
}
Dependencies
- Requires valid API credentials for Pipefy and the n8n Tools API.
- The node uses GraphQL requests to Pipefy's API endpoints.
- Proper configuration of these credentials in n8n is necessary for authentication and authorization.
Troubleshooting
- Missing or invalid Pipe ID: The node requires a valid Pipe ID to delete a pipe. If this is missing or incorrect, the node will throw an error indicating the Pipe ID is required.
- API authentication errors: Ensure that the API credentials are correctly set up and have sufficient permissions to delete pipes.
- Pipe not found or already deleted: If the specified pipe does not exist or has been deleted previously, the API may return a failure message.
- Network or API downtime: Temporary network issues or Pipefy API outages can cause failures; retrying later may resolve these.
If the node throws an error like "The operation "delete" is not supported", verify that the operation parameter is correctly set to "delete".