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, specifically providing access to various resources and operations within the platform. For the Consent Analysis resource with the Get Statistics operation, it fetches aggregated data from the consent dashboard. This is useful for analyzing user consent statistics, compliance metrics, and privacy-related insights.
Typical use cases include:
- Retrieving summarized consent data for reporting or auditing purposes.
- Monitoring consent trends over time.
- Filtering consent statistics by date ranges, device types, locations, or other criteria.
Example: A marketing team could use this node to pull consent statistics filtered by a specific date range and segment to understand how many users have given consent during a campaign period.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Collection of optional query parameters to customize the request. These include: - end: End date/time.- Fields[template]: Template fields.- filter: JSON filter object.- Various filter subfields like begin_date, end_date, from, rangeType, search, segment_id, sup_filters (device, location), to, types.- granularity: Data granularity.- include: Additional data to include.- page: Pagination info in JSON.- sort: Sorting options.- source: Source identifier.- start: Start date/time.- token: An API token (password type). |
Output
The output is a JSON array where each item corresponds to the response from the Commanders Act API for the requested statistics. The structure depends on the API's response but generally includes aggregated consent data such as counts, dates, segments, and other statistical information relevant to the consent dashboard.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The node uses the base URL
https://api.commander1.com/v2. - Proper configuration of credentials in n8n is necessary to authorize requests.
Troubleshooting
- Missing Credentials Error: If the API credentials are not set or invalid, the node will throw an error indicating missing credentials. Ensure that the API key/token is correctly configured.
- Required Parameter Missing: Some operations require specific IDs or parameters (e.g., Cookie ID, Report ID). For the Consent Analysis Get Statistics operation, ensure that any required query parameters are provided if needed.
- API Request Failures: Network issues, invalid tokens, or incorrect query parameters can 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 Errors: 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
- For detailed query parameter usage, consult the Commanders Act Consent Analysis API section in their official docs.