Cloud Trigger

To learn more about triggers in general, see Understanding Triggers.

Cloud trigger allows you to integrate your Loftware Cloud or on-premise Control Center with existing business systems that run in private clouds or in dedicated data centers. If an existing business system (e.g., SAP S/4HANA or Oracle NetSuite) produces an output, a cloud-hosted API enables you to send HTTP requests to Cloud Trigger.

Cloud Trigger allows you to locally print labels whose content originates from the cloud information systems. Because Cloud Trigger that runs on the local Automation server uses standard methods for accessing the cloud-based services, you can deploy local printing in a secure and time efficient way.

Cloud Trigger enables a secure and transparent way to integrate your local label printing using applications that communicate over the open Internet.

Compared to the HTTP Server Trigger, Cloud Trigger does not require you to open any inbound ports on your firewall. Cloud Trigger uses a dedicated Loftware Cloud-hosted API, that sends HTTP requests to Cloud Trigger to start label printing on your local Automation server.

Cloud Trigger opens outbound communication to Service Bus using the following order:

1. Legacy Service Bus mode (TCP ports 9350–9354)

2. AMQP with TLS (ports 5671–5672; may fall back via 80/443 depending on network)

3. HTTPS AMQP-over-WebSockets (port 443 only)

If ports 9350–9354 are allowed in the local Windows firewall, Cloud Trigger may connect to Service Bus directly over that TCP range. If you prefer HTTPS-only traffic (the primary benefit of Cloud Trigger), you might see Cloud Trigger running and able to connect to the cloud, but Cloud Trigger calls fail (for example, returning "404 device not connected").

To make a connection with Service Bus:

• Block ports 9350–9354 in the local Windows firewall.

• Block ports 5671–5672 in the local Windows firewall.

• Restart the Automation Service and redeploy the trigger. Cloud Trigger will then use port 443 (if it was not already).

Events with no effects on your printing process, where the connection commonly breaks in WebSockets mode:

• Automation runs Cloud Trigger and opens a connection to Service Bus lmscloud-bus-trigger-production.servicebus.windows.net.

• A client sends a request to the Cloud API labelcloudapi.onnicelabel.com.

• The Cloud API invokes Cloud Trigger function, which attempts to communicate with the device running Cloud Trigger.

Cases that can prevent your printing process, where the connection commonly breaks in WebSockets mode:

• Cloud Trigger function may need to open an additional connection via a Service Bus relay host (for example, g6-prod-db4-008-sb.servicebus.windows.net) to send the data (this is often blocked)..

• The relay connection can't be established, Cloud Trigger function can't deliver data to the device and the Cloud API returns an error such as "404 device not connected".

To resolve the last two cases, allow outbound connectivity to the Service Bus relay endpoints. Because these relay endpoints are Microsoft-managed and dynamic, you can't rely on a fixed IP address or a fixed hostname; you must allow the broader subnet range (based on Microsoft public Service Tag data) and/or use wildcard hostnames if your security tooling supports it.

Examples of relay hostnames (these can vary):

g6-prod-db4-008-sb.servicebus.windows.net

g25-prod-db4-008-sb.servicebus.windows.net

g11-prod-db4-008-sb.servicebus.windows.net

IP ranges are part of the larger range discussed in the Service Tag data (example range: 52.169.0.0/16).

Wildcard allowlist examples:

• *-sb.servicebus.windows.net

• *-prod-*-*-sb.servicebus.windows.net

Add these as outbound allowlist entries. The relay hosts are provided by Microsoft; Loftware doesn'tt control them and they change over time, so a fixed list can't be provided.

When deploying Cloud Trigger, you have two options:

• Deploying Cloud Trigger with Loftware Cloud

• Deploying Cloud Trigger with your on-premise Control Center

Both options are equal in terms of offered functionalities. Choose your preferred option based on your available infrastructure.