Actions83
- 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
Overview
This node integrates with the Commanders Act API, allowing users to manage various resources such as sources, destinations, cookie scanner settings, event enrichments, and more. Specifically for the Source resource with the Update Source operation, it enables updating an existing source's details by sending a PATCH request to the API.
Typical use cases include:
- Modifying configuration or metadata of a data source in Commanders Act.
- Automating updates to sources based on external triggers or workflows.
- Integrating source management into broader data governance or marketing automation pipelines.
Example: Updating a source's name or connection parameters dynamically when changes occur in your environment.
Properties
| Name | Meaning |
|---|---|
| Source ID | The unique identifier of the source to update. |
| Query Parameters | Optional additional query parameters to customize the API request. Includes filters, sorting, pagination, date ranges, etc. |
| Request Body | JSON object containing the fields and values to update on the source. |
The Query Parameters collection supports many optional parameters such as:
end,start: Date/time boundaries for filtering.filterand its nested options: Various filtering criteria.granularity,include,page,sort: Control over data granularity, included fields, pagination, and sorting.token: An optional token parameter (password type).
Output
The node outputs the JSON response from the Commanders Act API after performing the update operation. The output structure depends on the API's response but generally includes the updated source details or status information.
If the API returns no content (HTTP 204), the node outputs a JSON object indicating "204 No Content".
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Commanders Act API.
- The base URL used is
https://api.commander1.com/v2. - Proper configuration of the API credentials in n8n is necessary before using this node.
Troubleshooting
- Missing Credentials Error: If the API credentials are not set or invalid, the node will throw an error indicating missing credentials.
- Required Parameter Missing: For the Update Source operation, if the Source ID is not provided, the node throws an error stating that the Source ID is required.
- API Errors: Any errors returned by the Commanders Act API will be wrapped and thrown as node API errors with descriptive messages.
- Invalid JSON in Request Body: The request body must be valid JSON; otherwise, parsing errors may occur.
- Unexpected Response Format: If the API returns a string that cannot be parsed as JSON, the node attempts to return it as plain text.
To resolve issues:
- Ensure all required parameters are provided.
- Verify API credentials and permissions.
- Validate JSON syntax in the request body.
- Check network connectivity and API endpoint availability.
Links and References
- Commanders Act API Documentation (official API docs)
- n8n documentation on HTTP Request Node for understanding API calls
- General REST API best practices for PATCH operations