Actions32
- Card Actions
- Organization Actions
- Pipe Actions
- Phase Actions
- Table Actions
- Table Record Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy API to manage users within an organization, specifically allowing you to set a user's role. The "Set Role" operation updates the role of an existing user in a specified organization.
Common scenarios where this node is beneficial include:
- Managing team permissions by promoting or demoting users (e.g., changing a member to an admin).
- Automating organizational role assignments based on workflow triggers.
- Ensuring correct access levels for users in Pipefy organizations.
Practical example:
- Automatically assign the "Admin" role to a user after they complete a certain onboarding process.
- Change a user's role to "Guest" when they are temporarily restricted from full access.
Properties
| Name | Meaning |
|---|---|
| Organization ID | The ID of the organization where the user's role will be set. |
| User ID | The ID of the user whose role is being updated. |
| Role | The role to assign to the user. Options: Admin, Member, Guest. |
Output
The output JSON contains a single field indicating the success status of the role update operation:
{
"success": true
}
success: A boolean indicating whether the role was successfully set.
No binary data is output by this node.
Dependencies
- Requires an active connection to the Pipefy API via an API key credential configured in n8n.
- The node sends GraphQL requests to the Pipefy API endpoint (
https://api.pipefy.com/graphql).
Troubleshooting
Common issues:
- Invalid or missing organization ID or user ID can cause errors.
- Insufficient permissions of the API key may prevent role changes.
- Network connectivity issues can cause request failures.
Error messages and resolutions:
"An unknown error occurred": Check API credentials and network connection.- API errors related to authorization: Ensure the API key has sufficient rights to modify user roles.
- Validation errors about IDs: Verify that the provided organization and user IDs exist and are correct.