Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts 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 deletes a member from a specific team within an account. It is useful in scenarios where you need to manage team memberships dynamically, such as removing users who no longer require access or have left the organization. For example, if a user leaves a project or company, this operation can be used to revoke their team membership programmatically.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account |
| Team Id | Identifier of the team |
| Member Id | Identifier of the member (userId in Payhawk) |
Output
The output JSON will typically confirm the deletion of the team member. It may include status information or details about the removed member. The node does not output 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 Payhawk API to perform the delete operation.
Troubleshooting
Common issues:
- Invalid or missing identifiers (Account Id, Team Id, Member Id) will cause the operation to fail.
- Authentication errors if the API key or credentials are incorrect or missing.
- Network or connectivity issues preventing communication with the API.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly configured and valid.
- "Not Found": Verify that the Account Id, Team Id, and Member Id exist and are correct.
- "Bad Request": Ensure all required properties are provided and formatted properly.
Links and References
- Payhawk API Documentation (example link, replace with actual)
- n8n documentation on creating custom nodes