Actions108
- 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
- Create Web Constraint
- Create Web Container
- Create Web Perimeter
- Create Web Tag
- Create Web Trigger
- Delete Web Constraint
- Delete Web Container
- Delete Web Perimeter
- Delete Web Tag
- Delete Web Trigger
- Get Web Constraint
- Get Web Perimeter
- Get Web Tag
- Get Web Trigger
- List Web Constraints
- List Web Containers
- List Web Perimeters
- List Web Tags
- List Web Triggers
- Revert Web Tag
- Update Web Constraint
- Update Web Container
- Update Web Perimeter
- Update Web Tag
- Update Web Trigger
- Web Containers Variable Actions
- Create Web Datalayer Variables
- Create Web Datalayer Variables Category
- Create Web Internal Variables
- Delete Web Datalayer Variables
- Delete Web Datalayer Variables Category
- Delete Web Internal Variables
- Get Web Datalayer Variables
- Get Web Internal Variables
- List Web Datalayer Variables
- List Web Internal Variables
- Workspace Actions
Overview
This node integrates with the Commanders Act API to perform various operations related to monitoring and managing events, alerts, notifications, and other resources within the Commanders Act platform. Specifically, for the Monitoring resource and the List Events Collection Statistics operation, it retrieves statistical data about event collections, which can be useful for tracking event volumes, performance, or health metrics over time.
Typical use cases include:
- Monitoring event collection statistics to analyze data ingestion trends.
- Generating reports on event activity for operational insights.
- Automating alerting or notification workflows based on event statistics.
For example, a user might configure this node to periodically fetch event collection statistics filtered by date ranges or specific event types to feed into dashboards or trigger downstream automation.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of optional parameters to customize the API request. These include: - end: End date/time filter.- Fields[template]: Template fields selection.- filter (and subfields): JSON filters such as date ranges, search terms, segment IDs, device/location filters, event types, etc.- granularity: Data granularity level.- include: Additional data to include.- page: Pagination details in JSON.- sort: Sorting options in JSON or string format.- source: Source identifier.- start: Start date/time filter.- token: An optional token for authentication or pagination (password type). |
Output
The node outputs an array of JSON objects representing the response from the Commanders Act API for the requested event collection statistics. The structure depends on the API response but generally includes statistical data about events collected, such as counts, timestamps, and possibly metadata about the event sources or filters applied.
If the API returns no content, the node outputs a JSON object indicating "Status Code": "204 No Content".
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The base URL used is
https://api.commander1.com/v2. - The node expects the user to provide valid credentials with a site ID and API token.
- Proper configuration of the API credentials in n8n is necessary before using this node.
Troubleshooting
- Missing Credentials Error: If the node throws an error about missing API credentials, ensure that the Commanders Act API credentials are properly configured in n8n.
- Required Parameter Missing: Some operations require specific IDs or parameters (e.g., Alert ID, Cookie ID). For the List Events Collection Statistics operation, ensure that query parameters are correctly set if needed.
- API Errors: Errors returned from the API will be wrapped and shown with the message prefix "Error calling Commanders Act API". Check the API token validity, permissions, and network connectivity.
- Empty Response: If the API returns no data, the node outputs a 204 status code message. Verify the query parameters and date ranges to ensure data exists for the requested period.
Links and References
- Commanders Act API Documentation (general reference; actual link may vary)
- n8n documentation on HTTP Request Node for understanding how API calls are made
- Commanders Act official website: https://www.commandersact.com
This summary focuses on the Monitoring resource and the List Events Collection Statistics operation as requested, describing the input properties relevant to query customization and the expected output format.