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 deletes a team member from a specified team within a group. 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, an admin can automate the removal of a user from a project team when their role changes or when they leave the company.
Properties
| Name | Meaning |
|---|---|
| Group Id | Identifier of the Group |
| Team Id | Identifier of the Team |
| Member Id | Identifier of the member (userId in Payhawk) |
Output
The output JSON typically contains the result of the delete operation, which may include confirmation of successful deletion or relevant status information. The node does not explicitly handle binary data output for this operation.
Dependencies
- Requires an API key credential for authenticating with the external service.
- The node interacts with the Payhawk API endpoint configured via credentials.
- Proper configuration of the base URL and authentication token in n8n credentials is necessary.
Troubleshooting
Common Issues:
- Invalid or missing Group Id, Team Id, or Member Id will cause the operation to fail.
- Authentication errors if the API key or credentials are incorrect or expired.
- Network connectivity issues preventing communication with the API.
Error Messages:
- "Unauthorized" or "Authentication failed": Check API credentials and permissions.
- "Not Found" or "Resource does not exist": Verify that the Group Id, Team Id, and Member Id are correct.
- "Bad Request": Ensure all required parameters are provided and correctly formatted.
Links and References
- Payhawk API Documentation (example link, replace with actual)
- n8n documentation on creating custom nodes