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 allows you to add a member to a specific team within a group. It is useful in scenarios where you manage organizational structures, such as assigning users to teams for collaboration or access control purposes. For example, in a corporate environment, you might use this node to programmatically add an employee to a project team with defined roles.
Properties
| Name | Meaning |
|---|---|
| Group Id | Identifier of the Group to which the team belongs. |
| Team Id | Identifier of the Team where the member will be added. |
| Member Id | User ID of the member to be added to the team (specific to the system, e.g., Payhawk). |
| Roles | JSON array defining the roles granted to the team member (e.g., ["admin", "editor"]). |
Output
The node outputs JSON data representing the result of the add-member-to-team operation. This typically includes confirmation details such as the updated team membership or status of the request. The output does not include binary data.
Dependencies
- Requires an API key credential for authentication with the external service.
- Needs configuration of the base URL for the API endpoint.
- Depends on the external service's API that manages groups, teams, and members.
Troubleshooting
- Common issues:
- Invalid or missing Group Id, Team Id, or Member Id can cause the operation to fail.
- Incorrectly formatted Roles JSON may lead to parsing errors.
- Authentication failures if the API key or credentials are not set properly.
- Error messages:
- "Member not found" indicates the provided Member Id does not exist.
- "Team not found" or "Group not found" means the specified identifiers are invalid.
- "Unauthorized" suggests issues with API credentials; verify and update them.
- Resolutions:
- Double-check all IDs for correctness.
- Validate the Roles JSON format before input.
- Ensure API credentials are correctly configured in n8n.
Links and References
- Refer to the external API documentation for managing groups and teams for detailed information on roles and permissions.
- n8n documentation on setting up API credentials and HTTP request nodes for further customization.