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 removes managers associated with a specific custom field value within an account. It is useful in scenarios where you need to revoke managerial permissions or roles linked to particular custom field values, such as when updating team responsibilities or cleaning up access controls based on dynamic custom field assignments.
For example, if your system uses custom fields to tag users with certain roles or departments, and you want to remove all managers assigned to a specific custom field value (e.g., "Project X Manager"), this operation will facilitate that by targeting the exact custom field and its value.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account where the custom field exists. |
| Custom Field Id | Identifier of the custom field from which managers will be removed. |
| Custom Field Value Id | Identifier of the specific value of the custom field for which managers should be removed. |
Output
The node outputs JSON data representing the result of the removal operation. This typically includes confirmation of success or details about the affected managers. The exact structure depends on the API response but generally confirms which managers were removed or if the operation was successful.
No binary data output is involved.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to interact with the external service managing custom fields and managers.
- The node relies on an HTTP-based API endpoint to perform the removal action.
- Proper base URL and authentication credentials must be set up in n8n for the API requests to succeed.
Troubleshooting
Common issues:
- Invalid or missing Account Id, Custom Field Id, or Custom Field Value Id can cause the operation to fail.
- Authentication errors due to incorrect or expired API credentials.
- Network connectivity problems preventing API calls.
- Insufficient permissions to modify managers for the specified custom field.
Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and ensure they are valid.
- "Not Found" or "Invalid ID": Verify that the Account Id, Custom Field Id, and Custom Field Value Id are correct and exist.
- "Permission denied": Ensure the authenticated user has rights to remove managers for the given custom field.
Resolving these usually involves verifying input parameters, refreshing credentials, and confirming user permissions.
Links and References
- Refer to the API documentation of the service managing custom fields and managers for detailed information on identifiers and permissions.
- n8n documentation on setting up API credentials and HTTP request nodes may help configure the environment properly.