Commanders Act icon

Commanders Act

Use the Commanders Act API
Join our community

Actions108

Overview

This node integrates with the Commanders Act API to retrieve detailed information about event delivery issues for a specified issue ID. Specifically, the "Get Destination Delivery Issue Details" operation fetches comprehensive details related to a particular delivery issue, including the associated event, the request sent to the connector API, and the response received from the connector API.

This node is useful in scenarios where you need to diagnose or audit problems encountered during event delivery to external destinations. For example, if an event fails to be delivered correctly, this node helps you obtain detailed diagnostic data to understand what went wrong, enabling troubleshooting and resolution.

Practical examples:

  • Fetching detailed error reports for failed event deliveries to analyze root causes.
  • Auditing event delivery requests and responses for compliance or debugging.
  • Integrating with monitoring workflows to automatically alert on specific delivery issues.

Properties

Name Meaning
Issue ID The unique identifier of the event delivery issue to retrieve details for.
Query Parameters Optional additional parameters to filter or modify the API request. Includes options like:
- End (string): End date/time for filtering.
- Fields[template] (string): Template fields selection.
- Filter (JSON): Complex filter criteria in JSON format.
- Filter[begin_date], Filter[end_date], Filter[from], Filter[to] (string): Date/time filters.
- Filter[rangeType], Filter[search], Filter[segment_id], Filter[types] (string): Various filters.
- Filter[sup_filters][device][], Filter[sup_filters][location][] (string): Sub-filters arrays.
- Granularity (string): Data granularity level.
- Include (string): Additional data to include.
- Page (JSON): Pagination settings.
- Sort (JSON/string): Sorting options.
- Source (string): Source identifier.
- Start (string): Start date/time for filtering.
- Token (password string): Optional token for authentication or access control.

Output

The node outputs a JSON array where each item contains the detailed information about the specified event delivery issue. This includes:

  • The related event data that experienced the delivery issue.
  • The exact request payload sent to the connector API.
  • The response received from the connector API, which may contain error messages or status codes.

If the API returns no content, the output will indicate a "204 No Content" status.

The node does not output binary data.

Dependencies

  • Requires an active connection to the Commanders Act API.
  • Requires valid API credentials including a site ID and an API token.
  • The node uses HTTP requests to the Commanders Act API endpoint https://api.commander1.com/v2.
  • Proper configuration of the API credentials within n8n is necessary before use.

Troubleshooting

  • Missing Credentials Error: If the node throws an error about missing API credentials, ensure that the Commanders Act API credentials are properly configured in n8n.
  • Required Parameter Missing: The node requires the "Issue ID" property for this operation. If omitted, it will throw an error indicating the missing parameter.
  • API Errors: Errors returned by the Commanders Act API will be wrapped and presented as node errors. Check the error message and stack trace for details.
  • Empty Response: A "204 No Content" status means no data was returned for the given issue ID; verify the correctness of the issue ID and query parameters.
  • Invalid JSON in Query Parameters or Request Body: Ensure that any JSON input in query parameters or request body is well-formed.

Links and References

Discussion