Actions11
Overview
This node enables advanced management of Pipefy pipes, specifically allowing users to create, update, delete, and manage phases within a pipe. The "Create Phase" operation focuses on adding a new phase to an existing pipe in Pipefy. This is useful for workflows that require dynamic structuring of process stages, such as project management pipelines, sales funnels, or customer support queues.
Practical examples:
- Adding a new approval stage to a project pipeline.
- Creating a "Done" phase to mark completed tasks.
- Setting up a phase where cards can be created directly by team members.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | The unique identifier of the pipe where the new phase will be created (required). |
| Phase Name | The name of the new phase to be created (required). |
| Phase Options | Additional optional settings for the phase: |
| - Description: Text describing the phase. | |
| - Done Phase: Boolean indicating if this phase marks completion ("done"). | |
| - Can Receive Cards Directly: Boolean indicating if cards can be created directly here. |
Output
The output JSON contains details of the newly created phase within the specified pipe. It includes all relevant information about the phase such as its ID, name, description, status as a done phase, and whether it can receive cards directly.
Example output structure (simplified):
{
"id": "phase_id",
"name": "Phase Name",
"description": "Optional description",
"done": false,
"canReceiveCardDirectly": true
}
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Pipefy API.
- Requires another API authentication token for the n8n Tools API.
- The node uses GraphQL queries and mutations to interact with Pipefy's backend.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing Required Fields: Errors occur if "Pipe ID" or "Phase Name" are not provided. Ensure these fields are filled.
- API Authentication Failures: If credentials are invalid or missing, the node will fail to connect to Pipefy.
- Permission Issues: The authenticated user must have permission to modify the specified pipe.
- Invalid Pipe ID: Providing a non-existent or incorrect pipe ID will result in errors from the API.
- Network Issues: Connectivity problems may cause request failures; verify network access to Pipefy API endpoints.
Common error messages:
"The operation "createPhase" is not supported"— indicates an unsupported operation was selected; ensure "Create Phase" is chosen.- Validation errors mentioning missing required parameters like "Pipe ID" or "Phase Name".
- API response errors indicating permission denied or resource not found.
Resolving these typically involves verifying input parameters, checking credentials, and ensuring the user has appropriate permissions.