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 supporting operations related to "Web Containers Variable" resource. The selected operation "List Web Datalayer Variables" allows users to retrieve a list of web datalayer variables configured in their Commanders Act environment.
This node is beneficial for scenarios where you want to automate the retrieval and processing of web datalayer variables from Commanders Act, such as syncing these variables with other systems, auditing variable configurations, or triggering workflows based on variable data.
For example, a marketing analyst could use this node to fetch all datalayer variables periodically to monitor changes or validate tracking setups across multiple websites managed via Commanders Act.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of optional query parameters to filter or modify the list request. These include: |
| - End (string) | |
| - Fields[template] (string) | |
| - Filter (JSON) | |
| - Filter[begin_date] (string) | |
| - Filter[end_date] (string) | |
| - Filter[from] (string) | |
| - Filter[rangeType] (string) | |
| - Filter[search] (string) | |
| - Filter[segment_id] (string) | |
| - Filter[sup_filters][device][] (string) | |
| - Filter[sup_filters][location][] (string) | |
| - Filter[to] (string) | |
| - Filter[types] (string) | |
| - Granularity (string) | |
| - Include (string) | |
| - Page (JSON) | |
| - Sort (JSON or string depending on context) | |
| - Source (string) | |
| - Start (string) | |
| - Token (string, password type) |
These parameters allow fine-tuning the API request, such as filtering by date ranges, sorting results, pagination, and specifying which fields to return.
Output
The output is an array of JSON objects representing the response from the Commanders Act API for the requested web datalayer variables. Each item corresponds to a datalayer variable with its associated properties as returned by the API.
If the API returns no content, the node outputs a JSON object indicating "204 No Content".
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The node uses the base URL
https://api.commander1.com/v2for all requests. - Proper configuration of the API credentials within 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 key is correctly set up in n8n credentials.
- Required Parameter Missing: For some operations, specific IDs or parameters are mandatory. For example, if a required ID parameter is missing, the node will throw an error indicating which parameter is needed.
- API Request Errors: Network issues or invalid 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.
- Empty Response: If the API returns no data, the node outputs a status code message "204 No Content". Verify your query parameters or API permissions if unexpected.
Links and References
- Commanders Act API Documentation (official API docs)
- n8n Documentation (for general usage of nodes and credentials)