Actions11
Overview
The node enables interaction with Pipefy pipes, specifically allowing users to create, update, retrieve, delete, and manage pipes within an organization. The "Get Many" operation fetches multiple pipes from a specified organization, up to a user-defined limit. This is useful for workflows that need to list or process multiple pipes at once, such as reporting on pipe statuses, syncing pipe data with other systems, or automating bulk operations across pipes.
Practical example: A user wants to retrieve all pipes in their organization (up to 50) to generate a dashboard overview of active workflows or to trigger further automation based on pipe attributes.
Properties
| Name | Meaning |
|---|---|
| Organization ID | The unique identifier of the organization from which to retrieve pipes. Required field. |
| Limit | Maximum number of pipes to return. Accepts values from 1 to 50. Defaults to 50. |
Output
The output is an array of pipe objects under the json field. Each object represents a pipe retrieved from the organization and contains its details as provided by the Pipefy API. The exact structure includes pipe properties such as ID, name, description, color, and other metadata related to each pipe.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Pipefy API.
- Requires an additional API key credential for the n8n Tools API used internally.
- The node uses GraphQL queries/mutations to interact with the Pipefy API.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing or invalid Organization ID: The node validates that the Organization ID is provided. If missing or incorrect, it will throw an error indicating the required field is not set.
- Limit out of range: The limit must be between 1 and 50. Setting a value outside this range may cause errors or unexpected behavior.
- API authentication errors: Ensure that the API keys are valid and have sufficient permissions to access the organization's pipes.
- Network or API downtime: Temporary failures in connecting to the Pipefy API can cause errors; retrying later or checking network connectivity may help.
- Unexpected response format: If the Pipefy API changes, the node might fail to parse the response correctly.