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 allowing users to update an existing Destination resource. The "Update Destination" operation modifies the details of a specified destination within the Commanders Act platform.
Typical use cases include:
- Automating updates to destination configurations in marketing or analytics platforms.
- Synchronizing destination settings based on external triggers or workflows.
- Managing integration endpoints dynamically without manual intervention.
For example, you might update a destination's configuration to change its parameters or credentials when a campaign changes or when new data sources become available.
Properties
| Name | Meaning |
|---|---|
| Destination ID | The unique identifier of the destination to update. |
| Query Parameters | Optional additional parameters to customize the request. Includes options like end, filter, page, sort, etc. These allow filtering, pagination, sorting, and other query customizations. |
| Request Body | JSON object containing the fields and values to update for the destination. This is the main payload sent in the update request. |
Details on Query Parameters (selected examples):
- end: End date/time filter.
- filter: JSON filter criteria.
- page: Pagination details as JSON.
- sort: Sorting instructions as JSON or string.
- token: An optional token parameter (password type).
Output
The node outputs the JSON response returned by the Commanders Act API after updating the destination. The output structure depends on the API response but generally includes the updated destination details or status information.
If the API returns a string, the node attempts to parse it as JSON; if parsing fails, it outputs the raw text. If no content is returned (HTTP 204), it outputs a status message indicating "204 No Content".
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Commanders Act API.
- Needs valid API credentials including a site ID and an API token.
- The base URL used is
https://api.commander1.com/v2. - The node expects the credentials to be configured in n8n with appropriate permissions to update destinations.
Troubleshooting
- Missing Credentials Error: If API credentials are not set or invalid, the node throws an error "Missing Commanders Act API Credentials". Ensure credentials are properly configured.
- Required Parameter Missing: If the Destination ID is not provided, the node throws "Destination ID is required". Always specify the destination to update.
- API Errors: Any errors from the API call will be wrapped and thrown as "Error calling Commanders Act API" with the original message and stack trace. Check the API documentation and ensure the request body and parameters are correct.
- Invalid JSON in Request Body: The request body must be valid JSON. Invalid JSON will cause parsing errors.
- Network Issues: Connectivity problems to the API endpoint can cause failures. Verify network access and API availability.
Links and References
- Commanders Act API Documentation (general reference for API endpoints and usage)
- n8n Documentation on Creating Custom Nodes
- REST API concepts for PATCH requests and JSON payloads
This summary focuses on the "Destination" resource and the "Update Destination" operation as requested.