Actions108
- Activity Log Actions
- Consent Analysis Actions
- Cookie Scanner Actions
- Web Container Actions
- Get Web Tag
- 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 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
- 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 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
Destination → Update Destination
AI-generatedOverview
This node operation updates an existing destination in the Commanders Act platform. It is useful for scenarios where you need to modify the configuration or details of a destination integration, such as changing its settings or updating its metadata. For example, you might update a destination to change its connection parameters or to enable/disable certain features.
Use Case Examples
- Updating a destination's configuration by providing the destination ID and the new settings in the request body.
- Modifying metadata of a destination to reflect changes in the integration requirements.
Properties
| Name | Meaning |
|---|---|
| Destination ID | The unique identifier of the destination to update. This is required to specify which destination to modify. |
| Query Parameters | Optional query parameters to customize the API request, such as filters, pagination, sorting, etc. |
Output
JSON
json- The JSON response from the Commanders Act API representing the updated destination details or status.
Dependencies
- Commanders Act API credentials (siteId and tokenAPI) are required for authentication.
Troubleshooting
- Ensure the Destination ID is provided; otherwise, the node will throw an error indicating the missing ID.
- Verify that the API credentials (siteId and tokenAPI) are correctly set and valid to avoid authentication errors.
- Check the request body JSON format for correctness when sending update data; malformed JSON will cause request failures.
- If the API returns an error, the node will throw a NodeApiError with the message from the API; review the error message and stack trace for debugging.