Data destinations (outgoing)

Data destinations are the outbound counterpart to data sources: instead of receiving data, they send it out. Create and manage them from the menu under Data destinations.

A destination is reusable: create it once. Any data piece can send through it with Trigger data destination. Destinations never send on their own.

For a send that belongs on this component only, use HTTP request, MQTT send, or WebSocket send in tap actions — no destination. MQTT and WebSocket still pick an existing connection. An HTTP data source is the opposite direction: it polls incoming data (or Trigger data source(s) does). See Tap actions.

On the Data destinations screen, swipe a row right to left to delete a destination.

The last setting in a destination editor is Data: your own notes or data, up to 5120 characters, as plain text or JSON. It is stored as is and not evaluated, and scripts cannot read it. Don't put secrets there. See Components.

Types of destinations

Type What it sends Typical setup
HTTP An Actions / Transformers pipe to a URL At least one HTTP request (POST by default), plus optional expressions, JSONPath, Lua, JavaScript, Stop pipeline, or Debounce. Headers, query or body parameters, Request timeout (ms) (10000 ms by default, 500–120000 ms), and TLS live on each request
MQTT A publish to one or more topics A shared MQTT connection, the topics to publish to, QoS, a retain flag, and, when the connection uses MQTT 5, content type, user properties, and Message expiry interval (s) (off by default)
WebSocket A message on a shared connection A shared WebSocket connection, and Message events for Socket.IO-style connections (message by default)

MQTT and WebSocket destinations reuse the same connections as your data sources. If the connection is down and its Keep connected is on, Routix Dash connects before sending. If Keep connected is off (or a Disconnect action is holding it down), the send fails until the connection is up again.

What gets sent

When a tap action triggers a destination:

When later requests need earlier data: add several HTTP requests to the list — for example authenticate or fetch a token first, then call the real endpoint with it. Requests run in order each time you trigger the destination. Extract fields from the first response with JSONPath or Lua, then reference them in the next request — for example Authorization: Bearer {{ value.access_token }}.

For HTTP, the list starts with value set to what the tap sends: the filled-in Text to send, or the current tap value when that is empty. If a request's body is empty after interpolation, that value becomes the request body instead. Set the content type yourself when you send a file or image.

For HTTP GET or HEAD, Routix Dash can ask whether anything changed since last time. HTTP 304 is success: the previous value is kept. On each HTTP request, Unchanged data sets what happens then:

Download in full on Trigger data destination (on by default) downloads the full response even if it hasn't changed.

Run if skips that row when the condition is not met. Do not run if skips it when the condition is met. If the condition cannot be evaluated, that row is also skipped, and the list continues. You can also add Stop pipeline or Debounce between requests.

Stop pipeline if failed is on unless you turn it off. A server error, a timeout, or a lost connection then stops the rest of the list. The request still replaces ctx.transport, and ctx.error is set. Turn it off for site monitoring so a later script can still run.

A Simple expression / JSONPath / Lua error stops the rest of the list. An empty or invalid URL, or an expression that can't be evaluated, also stops the rest of the list.

Getting a response back

For HTTP destinations only, turn on Apply result to pipeline on Trigger data destination to feed the list's final value into the rest of the tap run. A successful response body is parsed as JSON when possible. You can chain "send a command → read the response → show or forward the result" in one tap.

MQTT and WebSocket destinations don't return anything to the run — they just send.

Status

Each destination shows send health on its status dot (for example an HTTP error, or a connection that wasn't ready).

Typical uses

See Tap actions for Trigger data destination and the send actions that belong to this component only.

See also