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 an account team within the Payhawk system. It is useful for managing team memberships by programmatically assigning users to specific teams associated with accounts. Typical use cases include automating team management workflows, such as onboarding new employees or adjusting team compositions based on project needs.
For example, when a new employee joins a department, this node can be used to add their user ID to the relevant team with appropriate roles, ensuring they have the correct permissions and access immediately.
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-to-team operation. This typically includes confirmation details such as the updated team membership information or status messages from the API. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating requests to the Payhawk API.
- The node depends on the Payhawk REST API endpoint configured via credentials, including the base URL.
- The node uses standard HTTP headers for JSON content negotiation.
Troubleshooting
- Common issues:
- Invalid or missing Account Id, Team Id, or Member Id may cause the API call to fail.
- Incorrectly formatted Roles JSON can lead to parsing errors.
- Authentication failures if the API key credential is missing or invalid.
- Error messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set up.
- "Not Found" or "Invalid Account/Team/Member Id": Verify that the provided identifiers exist and are correct.
- "Bad Request" due to malformed Roles JSON: Ensure the Roles property is valid JSON and matches expected role values.
Links and References
- Payhawk API Documentation (for detailed API usage and role definitions)
- n8n documentation on creating custom nodes