Actions16
Overview
This node interacts with the Atomic BI API, specifically allowing users to create and manage data related to various resources. For the Campaigns resource with the Create operation, it enables users to create new campaign entries by specifying desired fields and parameters.
Common scenarios include automating campaign creation workflows, integrating campaign data into broader analytics pipelines, or managing marketing campaigns programmatically within n8n.
For example, a user might use this node to automatically create a campaign in Atomic BI when a new marketing event is triggered elsewhere, selecting only relevant fields such as "Name", "Description", and "Status" to be included in the output.
Properties
| Name | Meaning |
|---|---|
| Select | List of fields to select from the created campaign record. If left empty, all fields are selected. Options include: Id, Name, Description, Language, Space Id, Agent Id, Status, Created At, Updated At, Connection Id, Inbox Synced Until, Job Schedule, Fields, Filters, Orders, Presets, Completed At, Converted Title. |
Output
The node outputs JSON objects representing the created campaign(s). The structure of each JSON object corresponds to the selected fields specified in the "Select" property. If no fields are selected, all available fields for the campaign resource are returned.
No binary data output is indicated or supported by this node.
Dependencies
- Requires an API key credential for authenticating with the Atomic BI API.
- Needs configuration of the Atomic BI API base URL and API key within the node credentials.
- Relies on the Atomic BI API being accessible and operational.
Troubleshooting
- Invalid operation error: If an unsupported operation or resource is specified, the node throws an error indicating the invalid combination. Ensure that the operation is set to "Create" and the resource to "Campaigns".
- Authentication failures: If the API key or base URL is incorrect or missing, requests will fail. Verify credentials in the node settings.
- Empty or incorrect field selection: Selecting fields not supported by the API or leaving the "Select" property empty may result in unexpected output or errors. Use the provided options list to ensure valid selections.
- API connectivity issues: Network problems or API downtime can cause request failures. Check network connectivity and Atomic BI service status.
Links and References
- Atomic BI API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes