Actions16
Overview
This node interacts with the Atomic BI API to manage data resources. Specifically, for the Leads resource and the Delete operation, it allows users to delete lead records from Atomic BI based on specified filters and criteria.
Common scenarios where this node is beneficial include:
- Cleaning up outdated or irrelevant lead data in your Atomic BI database.
- Automating lead management workflows by removing leads that meet certain conditions.
- Integrating lead deletion as part of a larger data pipeline or CRM synchronization process.
For example, you could configure the node to delete all leads with a specific status or those created before a certain date, helping maintain an up-to-date lead list.
Properties
| Name | Meaning |
|---|---|
| Select | List of fields to select from each Lead record before deletion (optional). If left empty, all fields are selected. Available fields include Campaign Id, Space Id, Stage, Status, Email, First Name, Last Name, Company Name, Job Title, Location, and many more. |
| Filter | Filters to specify which Leads to include for deletion. Each filter consists of: Field (selectable from predefined fields or custom), Operator (Equals, Like, ILike, Contains), and Value. Multiple filters can be combined. |
| Offset | Starting offset of Leads to consider for deletion (optional). Useful for pagination or batch processing. |
| Limit | Maximum number of Leads to delete (optional). Limits the scope of deletion to avoid large-scale accidental removals. Maximum allowed is 1000. |
| Order By | Field by which to order the Leads before deletion (optional). Same field options as Select and Filter. |
| Order Direction | Direction of ordering: Ascending or Descending. Only applicable if "Order By" is set. |
| Additional Select | Advanced option to specify additional comma-separated select fields for Leads beyond those chosen in "Select". |
Output
The node outputs JSON objects representing the deleted Lead records. The structure of each output item corresponds to the selected fields of the Lead prior to deletion. This allows downstream nodes to access details about what was deleted.
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 within n8n credentials.
- Relies on the Atomic BI service being accessible and operational.
Troubleshooting
- Invalid operation error: If the node throws
Invalid operation: leads/Delete, ensure that the operation parameter is correctly set to "Delete" and the resource is "Leads". - Authentication errors: Verify that the API key credential is valid and has sufficient permissions to delete leads.
- Filter misconfiguration: Incorrect filter fields or operators may result in no leads being matched or unexpected deletions. Double-check filter settings.
- Limit and offset usage: Omitting limit or setting it too high might cause performance issues or unintended mass deletions. Use these properties carefully.
- API connectivity issues: Network problems or incorrect base URL configurations can prevent the node from communicating with Atomic BI.
Links and References
- Atomic BI API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General best practices for Data Deletion and Filtering (replace with relevant resource)