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
The "Update Event Enrichment" operation in the Commanders Act node allows users to update an existing event enrichment record via the Commanders Act API. Event enrichments are typically used to enhance or augment event data with additional information, which can be useful for analytics, reporting, or triggering specific workflows based on enriched event attributes.
This operation is beneficial when you need to modify details of a previously created event enrichment, such as changing its parameters or metadata. For example, if you have an event enrichment that categorizes user events by region and you want to update the criteria or add new fields, this operation enables you to do so programmatically within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Event Enrichment ID | The unique identifier of the event enrichment to update. Required for update operations. |
| Query Parameters | Optional parameters to customize the request, including filters, pagination, sorting, etc. |
| Request Body | JSON object containing the data to update the event enrichment with. |
Details on Query Parameters (selected examples)
end,start: Define time range boundaries.filter[begin_date],filter[end_date],filter[search], etc.: Various filtering options to refine the query.page: Pagination settings in JSON format.sort: Sorting instructions in JSON format.token: An optional token parameter (password type).
Output
The output is a JSON array where each element corresponds to the response from the API call for each input item processed. The JSON structure reflects the updated event enrichment resource returned by the Commanders Act API.
If the API returns a string response, the node attempts to parse it as JSON; if parsing fails, it outputs the raw text. If no content is returned (HTTP 204), the node outputs a status message indicating "204 No Content".
No binary data output is produced by this operation.
Dependencies
- Requires an active Commanders Act API credential with a valid site ID and API token.
- The node makes HTTP requests to the Commanders Act API endpoint at
https://api.commander1.com/v2. - Proper configuration of credentials in n8n is necessary to authenticate API calls.
Troubleshooting
- Missing Credentials: The node throws an error if the Commanders Act API credentials are not set or invalid.
- Missing Event Enrichment ID: For update operations, the node requires the event enrichment ID; absence will cause an error.
- Invalid JSON in Request Body: The request body must be valid JSON; malformed JSON will cause the API call to fail.
- API Errors: Any errors returned by the Commanders Act API are wrapped and rethrown with descriptive messages.
- Network Issues: Connectivity problems may cause request failures; ensure network access to the API endpoint.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n Documentation on Creating Custom Nodes