Actions83
- Activity Log Actions
- Consent Analysis Actions
- Cookie Scanner Actions
- Data Cleansing Actions
- Destination Actions
- Event Delivery Actions
- Event Enrichment Actions
- Live Report Builder Actions
- Mix Collect Redirect Rule Actions
- Monitoring Actions
- Normalized Datalayer Actions
- Segment Actions
- Source Actions
- Sources Data Quality Actions
- User Actions
- Web Container Actions
Overview
This node integrates with the Commanders Act API, allowing users to manage various resources such as sources, cookies, destinations, event enrichments, and more. Specifically, for the Source resource with the Create Source operation, it enables creating a new source in the Commanders Act platform by sending a POST request with the specified data.
Common scenarios where this node is beneficial include automating the creation and management of data sources within Commanders Act, integrating source setup into workflows, or dynamically adding sources based on external triggers.
For example, a marketing automation workflow could create a new data source automatically when a new campaign is launched, ensuring that all relevant data streams are properly configured without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of optional query parameters to customize the API request. Includes parameters like end, filter (with subfields such as begin_date, end_date, search, etc.), granularity, include, page, sort, source, start, and token. These allow filtering, sorting, pagination, and other query customizations. |
| Request Body | JSON object representing the body of the POST request to create the source. This should contain the details of the source to be created according to the Commanders Act API specification. |
Output
The node outputs an array of JSON objects representing the response from the Commanders Act API after attempting to create the source. The structure of the output JSON depends on the API's response but typically includes details about the newly created source or error information if the creation failed.
If the API returns a string response, the node attempts to parse it as JSON; if parsing fails, it outputs the raw text. If no content is returned (HTTP 204), it outputs a status message indicating "204 No Content".
The node does not output binary data.
Dependencies
- Requires an active connection to the Commanders Act API.
- Requires credentials containing a site ID and an API token for authentication.
- The base URL used for requests is
https://api.commander1.com/v2. - The node expects the API token to be provided via credentials and uses Bearer token authorization in the HTTP header.
Troubleshooting
- Missing Credentials Error: If the API credentials are not set or invalid, the node will throw an error indicating missing credentials. Ensure that valid API credentials (site ID and token) are configured in n8n.
- Required Parameter Missing: For the Create Source operation, if required parameters in the request body or query parameters are missing or malformed, the API may return errors. Validate the input JSON and query parameters carefully.
- API Errors: Any errors returned by the Commanders Act API will be wrapped and thrown as node API errors with descriptive messages. Check the error message and stack trace for details.
- Parsing Response Failures: If the API returns a non-JSON string response, the node will output the raw text. Unexpected response formats might indicate issues with the API or request.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and payloads)
- n8n documentation on Creating Custom Nodes
- n8n documentation on Using Credentials
This summary focuses on the Source resource and the Create Source operation as requested.