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 interact with various resources and operations provided by the platform. Specifically, for the Source resource with the List Sources operation, it fetches a list of sources from the Commanders Act system. This is useful for scenarios where you want to retrieve and process metadata about data sources managed in Commanders Act, such as for analytics, monitoring, or integration workflows.
Practical examples include:
- Automatically retrieving all available sources to synchronize them with another system.
- Filtering sources based on specific query parameters to analyze or report on subsets of data.
- Using the source list as input for further processing or enrichment in an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of optional parameters to filter, sort, paginate, or specify fields when listing sources. Options include: End, Fields[template], Filter (with subfields like begin_date, end_date, search, segment_id, sup_filters for device/location, types), Granularity, Include, Page, Sort, Source, Start, Token (API token). These allow fine-tuning the request to the API to get exactly the desired subset or view of sources. |
Output
The output is a JSON array where each item corresponds to a source object returned by the Commanders Act API. The structure of each source object depends on the API response but typically includes details about the source such as its ID, name, category, configuration, and other metadata.
If the API returns no content, the node outputs a status code message indicating "204 No Content".
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The base URL used for requests is
https://api.commander1.com/v2. - The node expects valid credentials configured in n8n for accessing the Commanders Act API.
- The node uses HTTP methods GET (for listing) and supports passing query parameters to customize the request.
Troubleshooting
- Missing Credentials Error: If the API credentials are not set or invalid, the node will throw an error indicating missing API credentials. Ensure that the API key/token is correctly configured in n8n.
- Required Parameter Missing: For some operations, certain IDs or parameters are mandatory. For the List Sources operation, no mandatory ID is required, but if you use filters or tokens incorrectly, the API might reject the request.
- API Errors: If the API returns an error, the node throws a detailed error including the message and stack trace. Check the API documentation for the meaning of error codes and ensure your query parameters are valid.
- Empty Response: If the API returns no data, the node outputs a "204 No Content" status. Verify that your query parameters are correct and that there are sources available in your account.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and parameters)
- n8n Documentation on Creating Custom Nodes
- URLSearchParams MDN Documentation (used internally for query parameter construction)