Actions11
Overview
This node interacts with Pipefy pipes, allowing users to perform various operations such as creating, updating, retrieving, and deleting pipes, as well as managing pipe members and phases. It is useful for automating workflows that involve organizing tasks or processes within Pipefy, a popular process management platform.
For the Get operation on the Pipe resource, the node retrieves detailed information about a specific pipe by its ID. This is beneficial when you need to fetch the current configuration or status of a pipe to use in subsequent workflow steps, such as reporting, decision-making, or synchronization with other systems.
Practical example:
You have an automation that triggers when a new card is created in Pipefy. Before processing, you want to get details about the pipe where the card was created to customize your workflow based on pipe-specific settings or metadata.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | The unique identifier of the pipe to retrieve. This is required to specify which pipe's details to fetch. |
Output
The output JSON contains the full details of the requested pipe as returned by the Pipefy API. This typically includes properties such as the pipe's ID, name, description, color, visibility (public/private), permissions, phases, and other metadata related to the pipe.
No binary data is output by this operation.
Example output structure (simplified):
{
"id": "string",
"name": "string",
"description": "string",
"color": "string",
"public": true,
"anyoneCanCreateCard": false,
"phases": [ /* array of phase objects */ ],
// ... other pipe-related fields
}
Dependencies
- Requires an API key credential for authenticating with Pipefy.
- Requires an additional API key credential for the n8n Tools API (used internally).
- The node uses internal utility functions to make GraphQL requests to Pipefy’s API endpoints.
Troubleshooting
- Missing or invalid Pipe ID: The node requires a valid Pipe ID to fetch pipe details. If the Pipe ID is missing or incorrect, the node will throw an error indicating the missing required field or that the pipe could not be found.
- Authentication errors: Ensure that the API credentials are correctly configured and have sufficient permissions to access the specified pipe.
- API rate limits or connectivity issues: Network problems or Pipefy API rate limiting may cause failures. Retrying after some time or checking network connectivity can help.
- Unsupported operation error: If the operation parameter is set incorrectly, the node will throw an error stating the operation is not supported.