ADS Publisher icon

ADS Publisher

Create a publisher to emit ADS events
Join our community

Overview

This node, named "ADS Publisher," is designed to publish events to an ADS (Agent Data Shuttle) system. It takes input data representing events and emits them through a configured ADS publisher connection. This node is useful in scenarios where you want to forward or broadcast event data from n8n workflows to an external ADS event handling or processing system.

Practical examples include:

  • Sending user activity logs or telemetry events from your workflow to an ADS event stream.
  • Publishing custom business events for downstream analytics or monitoring systems.
  • Integrating with an event-driven architecture where ADS acts as the event bus.

Properties

Name Meaning
ADS Publisher Name An identifier name for the ADS Publisher instance that will emit the events.

Output

The node outputs a JSON object containing the following fields:

  • ads_publish_remarks: A string message summarizing the result of the publish operation.
  • ads_publish_success: A boolean indicating whether the publishing was successful.
  • ads_publish_payloads: An array of the event payloads that were published.

If no input data is provided, the output will indicate no data was available to publish and provide an example payload format.

Dependencies

  • Requires an API key credential for connecting to the ADS system, including host, port, username, and password.
  • Uses the external @agentdatashuttle/adsjs library to create the publisher and send events.
  • The node expects the ADS credentials to be configured in n8n beforehand.

Troubleshooting

  • No input data error: If the node receives no input or empty JSON objects, it will not attempt to publish and instead returns a remark explaining the lack of data.
  • Invalid data format error: The node requires each input item to have event_name, event_description, and event_data fields. Missing or empty values in these fields cause an error with an example payload shown.
  • Publishing errors: Any failure during the event publishing process throws an error with details. Common causes might be incorrect credentials, network issues, or ADS service unavailability.
  • To resolve errors, verify that input data matches the expected structure, credentials are correct, and the ADS service is reachable.

Links and References

Discussion