Actions11
Overview
The node interacts with Pipefy pipes, enabling users to manage pipes and their members programmatically within n8n workflows. Specifically, the "Get Members" operation retrieves all members associated with a specified pipe. This is useful for scenarios where you need to audit or process pipe membership information, such as sending notifications to pipe members, synchronizing user roles, or generating reports on pipe access.
Practical example: You have a workflow that triggers when a pipe is updated, and you want to fetch all current members of that pipe to notify them about changes or update permissions in another system.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | The unique identifier of the pipe whose members you want to retrieve. |
Output
The output JSON contains detailed information about the pipe members. It includes an array of member objects representing each user associated with the pipe. Each member object typically contains user details and their role within the pipe.
No binary data is output by this operation.
Example output structure (simplified):
{
"id": "pipeId",
"members": [
{
"user": {
"id": "userId",
"email": "user@example.com",
"name": "User Name"
},
"roleNames": ["admin", "member"]
},
...
]
}
Dependencies
- Requires an API key credential for authenticating with the Pipefy API.
- Requires an additional API authentication token credential specific to the integration.
- The node uses internal utility functions to perform GraphQL requests to Pipefy's API endpoints.
Troubleshooting
- Missing or invalid Pipe ID: The node requires a valid Pipe ID to fetch members. If omitted or incorrect, it will throw an error indicating the missing required field.
- API authentication errors: Ensure that the provided API credentials are valid and have sufficient permissions to read pipe members.
- Network or API errors: Temporary network issues or Pipefy API downtime can cause failures. Retrying the workflow or checking Pipefy status may help.
- Permission denied: If the authenticated user does not have access to the specified pipe, the API will reject the request.