Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node interacts with the Pipefy GraphQL API to retrieve detailed information about a specific pipe within Pipefy. It is useful for workflows that need to fetch metadata or configuration details of pipes, such as their labels, members, phases, and webhooks. For example, you might use this node to automate reporting on pipe configurations, synchronize pipe data with other systems, or trigger actions based on pipe structure.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Pipefy API: either using a Service Account or a Personal Access Token. |
| Pipe ID | The unique identifier of the pipe to retrieve. |
| Include Labels? | Whether to include the labels associated with the pipe in the response (true/false). |
| Include Members? | Whether to include the members of the pipe in the response (true/false). |
| Include Phases? | Whether to include the phases of the pipe in the response (true/false). |
| Include Webhooks? | Whether to include the webhooks configured on the pipe in the response (true/false). |
Output
The node outputs a JSON array where each item corresponds to the retrieved pipe data. The JSON object includes the pipe's core details and optionally its labels, members, phases, and webhooks depending on the selected options.
If enabled, the output fields may contain:
- Labels: Array of label objects related to the pipe.
- Members: Array of user/member objects associated with the pipe.
- Phases: Array of phase objects defining stages within the pipe.
- Webhooks: Array of webhook configurations linked to the pipe.
No binary data output is produced by this node.
Dependencies
- Requires access to the Pipefy GraphQL API.
- Requires authentication via either a service account credential or a personal access token credential.
- Proper configuration of these credentials in n8n is necessary for successful API calls.
Troubleshooting
- Invalid Pipe ID: If the provided Pipe ID does not exist or is malformed, the node will fail to retrieve data. Verify the Pipe ID is correct.
- Authentication Errors: Using incorrect or expired credentials will cause authentication failures. Ensure the API key or token is valid and has sufficient permissions.
- API Rate Limits: Excessive requests may be throttled by Pipefy’s API. Implement retry logic or reduce request frequency if encountering rate limit errors.
- Missing Optional Data: If optional fields like labels or members are requested but not returned, verify that the pipe actually contains those elements.