Actions11
Overview
This node enables managing Pipefy pipes, specifically allowing you to remove a member from a pipe. It is useful in scenarios where you need to automate membership management within your Pipefy workflows, such as revoking access for users who no longer require it or managing team roles dynamically.
For example, if a team member leaves a project, this node can be used to automatically remove their membership from the relevant Pipefy pipe, ensuring proper access control without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | The unique identifier of the pipe from which a member will be removed. |
| User Email | The email address of the user to be removed as a member from the specified pipe. |
Output
The output JSON contains the result of the removal operation with the following fields:
success(boolean): Indicates whether the member was successfully removed.pipeId(string): The ID of the pipe from which the member was removed.userEmail(string): The email of the user that was attempted to be removed.message(string): A human-readable message indicating success ("Member removed successfully") or failure ("Failed to remove member").
No binary data is output by this operation.
Example output:
{
"success": true,
"pipeId": "12345",
"userEmail": "user@example.com",
"message": "Member removed successfully"
}
Dependencies
- Requires an API key credential for authenticating with the Pipefy API.
- Requires an additional API authentication token credential specific to the n8n Tools integration.
- The node uses internal utility functions to perform GraphQL requests to Pipefy's API endpoints.
Troubleshooting
- Missing Required Fields: If "Pipe ID" or "User Email" are not provided, the node will throw an error indicating the missing required field. Ensure these inputs are correctly set.
- API Authentication Errors: Failure to authenticate with Pipefy's API due to invalid or missing credentials will cause errors. Verify that the API keys and tokens are correctly configured in n8n.
- Member Not Found: If the specified user email is not a member of the pipe, the removal may fail silently or return a failure message. Confirm the user is currently a member before attempting removal.
- Permission Issues: The API user must have sufficient permissions to remove members from the pipe; otherwise, the operation will fail.