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 → Get Destination
AI-generatedOverview
This node interacts with the Commanders Act API to retrieve details of a specific Destination resource. It is useful for scenarios where you need to fetch detailed information about a particular destination integration within the Commanders Act platform, such as for monitoring, reporting, or configuration purposes.
Use Case Examples
- Retrieve details of a Destination by providing its Destination ID to understand its configuration and status.
- Use the node to fetch Destination data as part of an automated workflow to sync or audit integration settings.
Properties
| Name | Meaning |
|---|---|
| Destination ID | The unique identifier of the Destination to retrieve. This is required to specify which Destination's details to fetch. |
| Query Parameters | Optional query parameters to refine or filter the API request. Includes parameters like 'end', 'filter', 'granularity', 'include', 'page', 'sort', 'source', 'start', and 'token' to customize the data retrieval. |
Output
JSON
json- The JSON response from the Commanders Act API containing the details of the requested Destination.
Dependencies
- Commanders Act API credentials (siteId and tokenAPI) required for authentication.
Troubleshooting
- Ensure the Destination ID is provided; otherwise, the node will throw an error indicating the missing ID.
- Verify that the Commanders Act API credentials are correctly configured and valid to avoid authentication errors.
- Check the query parameters for correct formatting, especially JSON fields, to prevent request failures.
- Common error messages include missing required parameters (e.g., Destination ID) and API request failures, which can be resolved by providing the necessary inputs and verifying network connectivity.