ApplicationEdge 1.0.0

MQTT Trigger Node

The MQTT Trigger will fire a workflow whenever a message is published to a topic of your choosing on the Losant MQTT broker. If used within an Application Workflow or Experience Workflow, the node can also be configured to trigger whenever a message is published to one of your MQTT broker integrations.

MQTT Trigger

Node Properties

There are two properties that can be configured for the MQTT Trigger:

Broker

The MQTT broker that the workflow will trigger on. By default this is the Losant MQTT broker, but you may also choose one of your MQTT broker integrations. This option is not available in edge workflows; in that case, the node will always trigger against the Losant MQTT broker.

MQTT Topic

When the trigger is configured to use the default Losant MQTT broker, you must also define a single topic on which the workflow should trigger when a message is published to that topic. This must be a valid MQTT topic, and furthermore, it cannot be an MQTT system topic, or a Losant-specific topic.

MQTT Trigger Config

In the above example, the workflow will trigger whenever any message is published to the Losant broker on the MQTT topic “alerts/power”.

Single-level and multi-level wildcard topics such as custom/+/temperature or custom/# are valid.

Payload

The payload will include the MQTT message on the data field, as well as the standard workflow payload information. The triggerType will be “mqttTopic” when using the Losant broker, and “integration” when using one of your integrations.

When triggering from the Losant broker, the value of data for the MQTT Trigger will be a string (unlike most other triggers, where the value of the data field is an object). In the general case, an MQTT workflow payload triggered by the Losant broker will look like the following:

{
  "time": <time of the message>,
  "data": <the mqtt message payload as a string>,
  "applicationId": <id of the current application>,
  "applicationName": <name of the current application>,
  "triggerId": <id of the mqtt trigger>,
  "triggerType": "mqttTopic",
  "flowId": <id of the current workflow>,
  "flowName": <name of the current workflow>,
  "globals": <object of workflow globals>
}

An MQTT workflow payload triggered by a MQTT broker integration will look like the following:

{
  "time": <time of the message>,
  "data": {
    "message": <the mqtt message payload as a string>,
    "topic": <the topic the message was published on>
  },
  "applicationId": <id of the current application>,
  "applicationName": <name of the current application>,
  "triggerId": <id of the mqtt integration>,
  "triggerType": "integration",
  "flowId": <id of the current workflow>,
  "flowName": <name of the current workflow>,
  "globals": <object of workflow globals>
}

For the example workflow above (which is triggered from the Losant broker), a specific payload for a triggered workflow might look like this:

{
  "time": Fri Feb 19 2016 17:26:00 GMT-0500 (EST),
  "data": "machineOn",
  "applicationId": "568beedeb436ab01007be53d",
  "applicationName": "Embree",
  "triggerId": "alerts/power/#",
  "triggerType": "mqttTopic",
  "flowId": "56c74add04d0b50100043381",
  "flowName": "Power Usage Alert",
  "globals": {}
}