OpenRuna
Sign in
← Workflows

Receive messages for a MQTT queue

1 nodes · mqtt

Engine
n8n
Nodes
1
Trigger
scheduled/triggered
Source file
0992_Mqtt_Send_Triggered.json

Workflow flow

IntegrationsMqtt
100%
TRIGGER

MQTT Trigger

Mqtt

1 steps · flows top to bottom, branches left to right

Browse by integration

mqtt
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Receive messages for a MQTT queue (1-node n8n automation, mqtt) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

"Receive messages for a MQTT queue" automates a mqtt-to-mqtt flow in n8n across 1 nodes. 1 nodes · mqtt It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Share it with your team as a documented reference for scheduled/triggered automations in the mqtt stack.
  • Study how data moves from mqtt to mqtt before building your own variant.
  • Use it as a starting template when wiring mqtt — adjust node parameters to your accounts and record IDs.
  • Import "Receive messages for a MQTT queue" into n8n, reconnect credentials for mqtt, and run the same automation in your own workspace.

Example output

Imported into n8n, "Receive messages for a MQTT queue" exposes 1 configured nodes. Trigger type: scheduled/triggered. Integrations: mqtt. Set your credentials on the mqtt node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "Receive messages for a MQTT queue" into Claude and ask it to explain each of the 1 nodes. Claude is good at suggesting credential mappings for mqtt, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Receive messages for a MQTT queue" to your accounts — which mqtt credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 1 nodes.

Frequently asked questions

How do I import "Receive messages for a MQTT queue" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Receive messages for a MQTT queue" use?
It uses: mqtt. The flow diagram above shows how each service connects across the 1 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own mqtt and mqtt credentials in n8n after import.
What trigger type does "Receive messages for a MQTT queue" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Receive messages for a MQTT queue" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for mqtt.

Related resources