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, "Remove Account User," is designed to remove a specific user from an account within the system. It is useful in scenarios where you need to revoke access or manage team members associated with an account. For example, if an employee leaves a company or no longer requires access to certain resources, this operation can be used to efficiently remove their user association from the account.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account from which to remove the user. |
| User Id | Identifier of the user to be removed from the account. |
Output
The output of this operation typically includes a JSON object indicating the success or failure of the removal action. The exact structure is not detailed in the provided code, but generally, it would confirm that the user has been successfully removed or provide error details if the operation failed.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authentication to interact with the external service's API.
- The node depends on the external Zitadel API (as indicated by the description) or a similar account management API.
- Proper configuration of the base URL and authentication credentials in n8n is necessary for successful execution.
Troubleshooting
- Common Issues:
- Invalid or missing Account Id or User Id will cause the operation to fail.
- Authentication errors due to incorrect or missing API credentials.
- Network connectivity issues preventing communication with the external API.
- Error Messages:
- Errors related to authorization typically indicate problems with the API key or token; verify credentials.
- Not found errors may mean the specified account or user does not exist; double-check identifiers.
- Validation errors suggest required parameters are missing or malformed; ensure all required fields are correctly filled.
Links and References
- Zitadel API Documentation (example reference based on the description)
- n8n documentation on creating custom nodes