[Feature Request]: MQTT Support

[johntdyer]

Is there an existing feature request for this?

• I have searched the existing issues

What is your feature request?

Would love MQTT support for the "events", seem to be lacking today

Code of Conduct

• I agree to follow this project's Code of Conduct

[jhuckaby]

Interesting! This is the first I have ever heard of MQTT, so I need to do a lot of research.

What would the integration look like, exactly? By "events" I am assuming you mean "jobs" (a.k.a executions).

Should this work similarly to the MQTT node in n8n? https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.mqtt/

Trying to find examples of workflow automation apps that do MQTT, so I can get an idea of how the integration would work.

[johntdyer]

I mean my use case is super simple , I have a health check on my nodes which I push to mqtt ``` #!/bin/bash MQTT='192.168.120.254' ## Uptime TOPIC="home/sensors/$(hostname)/uptime" PAYLOAD=$(cat /proc/uptime | awk '{printf "%0.f", $1}') /usr/bin/mosquitto_pub -t "$TOPIC" -m "$PAYLOAD" -h "$MQTT" ``` but it would be nice to do this natively somehow , and I could totally see wanting to create more complicated workflows based on input from mqtt in the future Regards, John

…

On Apr 23, 2026, at 12:21 PM, Joseph Huckaby ***@***.***> wrote: jhuckaby left a comment (pixlcore/xyops#277) <#277 (comment)> Interesting! This is the first I have ever heard of MQTT, so I need to do a lot of research. What would the integration look like, exactly? By "events" I am assuming you mean "jobs" (a.k.a executions). Should this work similarly to the MQTT node in n8n? https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.mqtt/ Trying to find examples of workflow automation apps that do MQTT, so I can get an idea of how the integration would work. — Reply to this email directly, view it on GitHub <#277?email_source=notifications&email_token=AAAOG6QJ7MD6IOYMSV6YS4D4XI7IPA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMZQGYYDIOBXGQZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4306048742>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAOG6VHIV4PIQPZZWRIIG34XI7IPAVCNFSM6AAAAACYEBLE2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGMBWGA2DQNZUGI>. You are receiving this because you authored the thread.

[jhuckaby]

Oh, okay then. Well in that case, it seems like you could just create a Monitor Plugin which could run the script exactly like you have it there. Monitor plugins run every minute on all of your servers.

Taking it a step further, someone could probably easily create and submit a Marketplace Plugin that wraps this, so you don't need the /usr/bin/mosquitto_pub binary on all of your servers. It could use something like:

https://www.npmjs.com/package/mqtt

Dependencies like that are automatically installed as part of the Plugin system.

Just brainstorming ideas 😊

[CoreSec-xyz]

I think adding an MQTT trigger would be a great addition. Since most home automation systems are built around MQTT, it would ensure broad compatibility.

While professional enterprise environments often rely on Kafka or NATS, those are significantly more complex to set up and maintain.

[jhuckaby]

Please forgive me -- I am very new to this MQTT thing, so I am still having trouble conceptualizing how the integration would work. Are we talking about:

1. A heartbeat health check like @johntdyer describes above, where his servers push a health check event onto a MQTT queue every N minutes?
2. A more standard Event Plugin integration, where a xyOps job or workflow can activate an MQTT Plugin that pushes a custom message onto a queue?
3. An active persistent queue listener, which subscribes to a MQTT queue listening for specific events, and those events can trigger jobs to run inside xyOps?
4. All of the above?

I ask because each of these look very different in terms of integration, and what kind of code I have to write.

[CoreSec-xyz]

MQTT is remarkably simple.

It operates on a publish/subscribe architecture based on topics.

A trigger would subscribe to a specific topic and initiate a workflow as soon as a message arrives.

Conversely, a plugin could publish messages to a topic. This covers points 2 and 3 on your list.

I’ve already built a basic event for publishing messages using the Docker plugin and User Fields:

mosquitto_pub -i xyops -h {{ params.host }} -t "{{ params.topic }}" -m "{{ params.payload }}"

However, using a subscription as a trigger is a different challenge, as it requires a background process that constantly listens for incoming messages.