Most-used Mqtttrigger workflows
- N8n Complete Final (58 nodes)
- Real-time Iot Anomaly Detection with Mqtt, Gpt-4o-mini Ai, and Multi-channel Alerts — n8n Mqtttrigger workflow (28 nodes)
- Splitout Filter (26 nodes)
- Iot Button Remote / Spotify Control Integration with Mqtt — n8n Mqtttrigger workflow (26 nodes)
- Iot Sensor Monitoring with Gpt-4o Anomaly Detection, Mqtt & Multi-channel Alerts (21 nodes)
- Flow — n8n Mqtttrigger workflow (14 nodes)
- Smart Manufacturing — Mqtt to Influxdb (mqtt Trigger) (10 nodes)
- Code Schedule (ftp) — n8n Mqtttrigger workflow (6 nodes)
- Remote Iot Sensor Monitoring via Mqtt and Influxdb (6 nodes)
- Smart Manufacturing — Mqtt to Influxdb — n8n Mqtttrigger workflow (6 nodes)
N8N Complete Final. Uses telegramTrigger, dataTable, telegram, mqtt. Event-driven trigger; 58 nodes.
MQTT ingests real-time sensor data from connected devices. The workflow normalizes the values and trains or retrains machine learning models on a defined schedule. An AI agent detects anomalies, valid
Splitout Filter. Uses spotify, stickyNote, httpRequest, splitOut. Event-driven trigger; 26 nodes.
This template integrates an IOT multi-button switch (meant for controlling a dimmable light) with Spotify playback functions, via MQTT messages. This isn't likely to work without some tinkering, but s
{ "name": "IoT Sensor Data Aggregation with AI-Powered Anomaly Detection", "nodes": [ { "parameters": { "content": "## How it works\nThis workflow monitors IoT sensors in real-time. It ingests data vi
Flow. Uses agent, lmChatGoogleGemini, memoryBufferWindow, mqttTool. Event-driven trigger; 14 nodes.
Smart Manufacturing — MQTT to InfluxDB. Uses mqttTrigger, httpRequest. Event-driven trigger; 10 nodes.
Code Schedule. Uses ftp, scheduleTrigger, mqtt, mqttTrigger. Scheduled trigger; 6 nodes.
Remote IOT Sensor monitoring via MQTT and InfluxDB. Uses stickyNote, mqttTrigger, httpRequest. Event-driven trigger; 6 nodes.
Smart Manufacturing — MQTT to InfluxDB. Uses mqttTrigger, httpRequest. Event-driven trigger; 6 nodes.
A single workflow with 2 flows/paths that combine to handle the backup sequence for Zigbee device configuration from HomeAssistant / zigbee2mqtt. This provides a way to automate a periodic capture of
My workflow 4. Uses mqtt, mqttTrigger, discord. Event-driven trigger; 5 nodes.
Mammal Detection. Uses mqttTrigger, telegram, influxDb. Event-driven trigger; 7 nodes.
14 of 14 workflows in this view · Browse all →
FAQ
How many n8n Mqtttrigger workflows are in the catalog?
14 n8n workflows in AutomationFlows currently use the Mqtttrigger integration — triggers, actions, or both.
How do I connect Mqtttrigger in n8n?
After importing the workflow JSON, n8n will prompt for Mqtttrigger credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.
Can I combine these with other integrations?
Yes — most Mqtttrigger workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.