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 → Create Destination
AI-generatedOverview
This node interacts with the Commanders Act API to create a new destination within the Commanders Act platform. It is useful for automating the creation of destinations in marketing or data integration workflows, allowing users to programmatically add new destinations without manual API calls. For example, it can be used to add a new data integration endpoint as part of a larger data pipeline setup.
Use Case Examples
- Automate the creation of a new marketing data destination when onboarding a new campaign.
- Programmatically add destinations to Commanders Act as part of a CI/CD pipeline for data integrations.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | Optional query parameters to customize the API request, such as filters, pagination, sorting, and other parameters relevant to the destination creation endpoint. |
| Request Body | JSON object representing the destination details to be created. This contains the data payload sent to the API to define the new destination's properties. |
Output
JSON
id- The unique identifier of the created destination.name- The name of the created destination.type- The type/category of the created destination.status- The status of the created destination.createdAt- Timestamp when the destination was created.updatedAt- Timestamp when the destination was last updated.
Dependencies
- Commanders Act API
- An API key credential for authentication
Troubleshooting
- Missing or invalid API credentials will cause authentication errors. Ensure the API token is correctly set in the node credentials.
- Required parameters such as the request body must be provided and correctly formatted as JSON; otherwise, the API call will fail.
- If the destination ID is required for other operations but missing, the node will throw an error indicating the missing parameter.
- API rate limits or network issues may cause request failures; check connectivity and API usage limits.
Links
- Commanders Act API Documentation - Official API documentation for Commanders Act, useful for understanding available endpoints and request/response formats.