Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation updates the roles assigned to a specific member within a team of a group. It is useful in scenarios where you need to manage user permissions dynamically, such as promoting a team member to an admin role or restricting access by changing their roles. For example, in a corporate environment, when a team member’s responsibilities change, this node can update their roles accordingly without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Group Id | Identifier of the Group to which the team belongs. |
| Team Id | Identifier of the specific team within the group. |
| Member Id | Identifier of the member (user) whose roles are being updated. |
| Roles | JSON array specifying the roles granted to the team member. Example: ["admin","user"] |
Output
The node outputs JSON data representing the result of the update operation. This typically includes confirmation of the updated member roles and possibly the updated member object or status from the API response. The exact structure depends on the external API's response but generally confirms success or failure of the role update.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the external service managing groups, teams, and members.
- The node uses a base URL configured in credentials to send HTTP requests.
- The operation relies on a REST API endpoint that supports updating member roles within a team.
Troubleshooting
- Missing or invalid identifiers: Ensure that Group Id, Team Id, and Member Id are correctly provided and correspond to existing entities; otherwise, the API will return errors.
- Invalid roles format: The Roles property must be a valid JSON array. Malformed JSON or unsupported role names may cause request failures.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions to update team member roles.
- API connectivity issues: Check network connectivity and base URL configuration if requests fail to reach the API.
Common error messages might include:
- "Member not found" — check the Member Id.
- "Unauthorized" or "Forbidden" — verify API credentials and permissions.
- "Invalid roles format" — ensure the Roles JSON is correctly structured.
Links and References
- Refer to the external API documentation for details on roles management and required request formats.
- n8n documentation on using credentials and JSON input properties for dynamic data handling.