Search Crosser Knowledge Base

Invoke messages from external apps/systems

In most use cases, a flow is triggered from within by modules such as the Interval, Scheduler, or Subscriber. However, there may be situations where you need to trigger the flow based on events from an external system. This can be achieved by sending messages from external applications or systems using various methods:

HTTP Listener

The HTTP Listener monitors specific endpoints on the Node’s internal HTTP server. If the HTTP server is exposed, external clients can connect and trigger specific HTTP methods, depending on how the listener is configured.

Crosser Tech Tips 69_ Flow Example 1

MQTT Sub Client

For a more event-driven approach, external clients can publish messages to the Node’s internal MQTT Broker. In this setup, the flow begins with MQTT Sub Client modules that subscribe to specific topics on the internal broker.

Crosser Tech Tips 69_ Flow Example 2

About the author

David Nienhaus | Senior Solution Engineer

David is a Senior Solution Engineer at Crosser. He has over 15 years experience working with software integration and digitization projects for critical infrastructure.
His engineering background gives him the understanding and focus needed to solve customer use cases in the most efficient and successful way.