Actions16
Overview
This node interacts with the Atomic BI API to manage data resources. Specifically, for the Users resource with the Delete operation, it allows deleting user records from the Atomic BI system based on specified filters and criteria.
Common scenarios where this node is beneficial include:
- Automating user management workflows by programmatically removing users who meet certain conditions.
- Cleaning up inactive or obsolete user accounts in bulk.
- Integrating user deletion into larger data processing pipelines within n8n.
Example use case: Automatically delete users who have not logged in for a long time by applying a filter on the "last login" date field.
Properties
| Name | Meaning |
|---|---|
| Select | List of user fields to select (e.g., Id, Username, Name, Created At, Updated At, Email, Role, Api Key). Leave empty to select all fields. |
| Filter | Filters to apply when selecting users to delete. Each filter includes a field, operator (Equals, Like, ILike, Contains), and value. Supports custom fields. |
| Offset | Starting offset of users to return (for pagination). |
| Limit | Maximum number of users to process/delete. Maximum allowed is 1000. |
| Order By | Field by which to order the returned users (e.g., Id, Username, Name, etc.). |
| Order Direction | Direction of ordering: Ascending or Descending. |
| Additional Select | Advanced option to specify additional select fields as comma-separated values. |
Output
The node outputs JSON data representing the users affected by the operation. For the Delete operation, the output typically contains the details of the deleted users according to the selected fields.
The structure of each output item is an object with user properties as keys, matching the selected fields.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Atomic BI API.
- Needs proper configuration of the Atomic BI API base URL and API key in the node credentials.
- The node depends on the Atomic BI API being accessible and responsive.
Troubleshooting
- Invalid operation error: If you see
Invalid operation: users/DELETE, ensure that the operation parameter is correctly set to "DELETE" and the resource is "users". - API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Filter syntax issues: Incorrect filter definitions may cause the API to reject requests. Double-check field names, operators, and values.
- Limit and offset misuse: Setting very high limits or invalid offsets might cause performance issues or API errors.
- Empty selection fields: If no fields are selected, the node defaults to selecting all fields, which might be inefficient if only specific data is needed.
Links and References
- Atomic BI API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- General REST API best practices for filtering, pagination, and ordering.
Note: This summary is based solely on static analysis of the provided source code and property definitions. Runtime behavior may depend on external API responses and configurations.