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
Account Teams → Add Member To A Team
AI-generatedOverview
This node operation allows you to add a member to an account team within the Payhawk system. It is useful for managing team memberships by programmatically assigning users to specific teams and defining their roles within those teams. Typical use cases include automating team management workflows, onboarding new users into teams with predefined permissions, or synchronizing team membership from external systems.
For example, when a new employee joins a company, this node can be used to automatically add them to the appropriate account team with the correct roles assigned, ensuring they have the necessary access and permissions without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the team belongs. |
| Team Id | Identifier of the team to which the member will be added. |
| Member Id | User ID in Payhawk representing the member to add to the team. |
| Roles | JSON array specifying the roles granted to the team member (e.g., ["admin", "viewer"]). |
Output
The node outputs JSON data representing the result of the add member operation. This typically includes confirmation details such as the updated team membership information or status messages returned by the Payhawk API. The output does not include binary data.
Dependencies
- Requires an active connection to the Payhawk API.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- The base URL for the Payhawk API must be set in the node credentials configuration.
Troubleshooting
Common issues:
- Invalid or missing
Account Id,Team Id, orMember Idcan cause the operation to fail. - Incorrectly formatted
RolesJSON may lead to parsing errors. - Authentication failures if the API key or token is invalid or expired.
- Network connectivity problems preventing communication with the Payhawk API.
- Invalid or missing
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Verify that the API credentials are correctly configured and valid.
- "Invalid input" or "Bad Request": Check that all required fields (
Account Id,Team Id,Member Id,Roles) are provided and correctly formatted. - "Not Found": Confirm that the specified account, team, and member IDs exist in Payhawk.
- JSON parse errors on Roles: Ensure the Roles property contains valid JSON array syntax.
Links and References
- Payhawk API Documentation (for detailed API endpoints and payload structures)
- n8n Documentation (for general usage of custom nodes and credentials setup)