Actions16
Overview
This node integrates with the Atomic BI API to perform data operations. Specifically, for the "Leads" resource and the "Create" operation, it would allow users to create new lead entries in their Atomic BI dataset. This is useful for automating lead management workflows, such as adding new prospects from form submissions or CRM exports directly into Atomic BI for further analysis.
Typical use cases include:
- Automatically creating leads from marketing campaign responses.
- Syncing new contacts from external systems into Atomic BI.
- Enriching lead data by combining it with other workflow steps before creation.
However, based on the provided source code, only a "GET" operation is implemented. The "Create" operation is not explicitly handled in the execute() method, so this node currently supports fetching lead data but does not support creating leads yet.
Properties
| Name | Meaning |
|---|---|
| Select | List of fields to select (leave empty to select all fields). Options include: Campaign Id, Space Id, Stage, Status, Details, Messages, Selected Message, Created At, Updated At, Posts, Synced At, Visited At, Visit Count, Id, List Id, List Title, Background Url, Company Description, Company Employee Count, Company Founded, Company Industry, Company Location, Company Monthly Change, Company Name, Company Urn, Degree, Educations, Email, First Name, Handle, Hash Id, Headline, Inmail Restriction, Job Description, Job Seeker, Job Started On, Job Title, Last Name, Location, Num Of Connections, Num Of Shared Connections, Object Urn, Open Link, Owner Id, Pending Invitation, Phone Number, Positions, Premium, Profile Url, Skills, Summary, Unsnooze At, Website, Read Until |
Note: The property "Select" allows choosing which lead fields to retrieve when performing a GET operation.
Output
The output JSON structure corresponds to the lead data retrieved from Atomic BI. Each item contains key-value pairs for the selected lead fields. For example, if "First Name", "Last Name", and "Email" are selected, each output JSON object will have those properties populated with the lead's data.
If the limit parameter is set to 1, the output is a single-item array containing one JSON object; otherwise, it returns an array of JSON objects representing multiple leads.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating with the Atomic BI API.
- Needs the base URL of the Atomic BI API endpoint.
- Uses internal utility modules for building schema, filtering, and parameter handling.
- No additional external dependencies beyond the Atomic BI API.
Troubleshooting
- Unsupported Operation Error: If you attempt to use the "Create" operation (or any operation other than "GET"), the node will throw an error:
Invalid operation: <resource>/<operation>. This is because only the "GET" operation is implemented in the current version. - Authentication Issues: Ensure that the API key credential and base URL are correctly configured; otherwise, API requests will fail.
- Empty Results: If no leads match the filter criteria or if the "select" fields are incorrectly specified, the output may be empty or incomplete.
Links and References
- Atomic BI API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General REST API usage best practices
Summary: Although the user requested details for the "Leads" resource and "Create" operation, the bundled source code only implements the "GET" operation. Therefore, the node currently supports retrieving lead data with selectable fields but does not support creating leads yet.