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 Catalog Sources operation, it fetches a list of catalog sources from the Commanders Act system.
This node is beneficial in scenarios where you want to automate the retrieval of source catalogs for data integration, monitoring, or reporting purposes within your workflows. For example, you might use it to dynamically fetch available data sources before processing or syncing data across systems.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of optional parameters to filter, sort, paginate, or customize the list request. 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 parameters allow fine-tuning the catalog sources listing request. |
Output
The output is a JSON array containing the response data from the Commanders Act API for the catalog sources list. The structure depends on the API's response but generally includes details about each catalog source such as identifiers, names, categories, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The node makes HTTP requests to
https://api.commander1.com/v2endpoint. - Proper configuration of the API credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing Credentials Error: If the API credentials are not set or invalid, the node will throw an error indicating missing credentials. Ensure that a valid API authentication token is configured.
- Required Parameter Missing: Some operations require specific IDs or parameters. For the List Catalog Sources operation, ensure that query parameters are correctly formatted if used.
- API Request Errors: Network issues or incorrect parameters may cause API errors. The node surfaces these errors with messages prefixed by "Error calling Commanders Act API". Check the message and stack trace for details.
- Parsing Response Issues: If the API returns unexpected data formats, the node attempts to parse JSON; failures here may indicate API changes or malformed responses.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and parameters)
- n8n Documentation on Creating Custom Nodes