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 an account. 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, if a company wants to change a user's role from "viewer" to "editor" within a project team, this operation allows that update programmatically.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the team belongs. |
| Team Id | Identifier of the team within the account where the member's role will be updated. |
| 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 output contains a JSON object representing the updated state of the team member's roles within the specified team. This typically includes confirmation of the new roles assigned and possibly metadata about the update operation. The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing accounts and teams.
- The base URL for the API must be configured in the node credentials.
- The node depends on the external Payhawk API (or similar service) to perform the update operation.
Troubleshooting
- Invalid Identifiers: Errors may occur if the Account Id, Team Id, or Member Id do not exist or are incorrect. Verify these IDs before running the node.
- Malformed Roles JSON: The Roles property expects valid JSON. Invalid JSON syntax will cause parsing errors. Use proper JSON formatting.
- Permission Denied: If the API key lacks sufficient permissions to update team members, the request will fail. Ensure the API key has appropriate scopes.
- Network Issues: Connectivity problems with the API endpoint can cause timeouts or failures. Check network settings and API availability.
Links and References
- Payhawk API Documentation (example link; replace with actual)
- n8n Documentation on Custom Nodes