Arcflux Alpha is live — start building realtime AI workflows today.
// Realtime Triggers

Every event source. One trigger layer.

Webhooks, schedules, chat, the API — and live device streams over MQTT, NATS, and AMQP. Whatever fires, Arcflux turns it into a governed AI workflow.

Every workflow builder handles webhooks. The machines that run the real world don't speak webhooks — they speak MQTT, NATS, and AMQP. Everyone else makes you build and babysit a bridge service; Arcflux subscribes to your broker natively.

01 · device streams

Live device streams, first-class

  • Subscribe to broker topics the way you'd add a webhook — wildcards, QoS, connector health.
  • Sensors, vehicles, and machines trigger workflows directly. No bridge service.
  • Already run a broker? Keep it.Arcflux subscribes to MQTT, NATS, and AMQP — it doesn't replace your broker, it turns its events into governed AI action.
02 · software sources

The software sources

  • Webhookspoint your monitoring, forms, or product events at an Arcflux endpoint.
  • Schedulescron-style jobs, with interval floors per plan.
  • Chat & widgetconversations as triggers, including the embeddable widget.
  • APItrigger any flow programmatically from your own systems.

HTTP · MQTT · NATS · AMQP · CRON · CHAT live today — CoAP and MAVLink are on the roadmap.

03 · governed

Governed before it runs

Every source feeds one policy gate: dedupe, cooldown, throttle, condition, safety. Sensor noise and duplicate alerts drop before they spend a credit — and trigger-to-run pickup is under 100ms when they pass.

mqtt → work order
mqtt  sensors/7/temp  31.8C
→ policy gate  (dedupe · cooldown · condition)
→ agent checks maintenance runbook
→ work order drafted — paused for approval
// FAQ

Common questions

The short version of how realtime triggers works. Anything else: info@arcflux.ai.

No. Arcflux subscribes to your existing broker; nothing about your infrastructure changes.

Policy checks — dedupe, cooldown, throttle, condition, safety — run before the workflow does. Skipped events cost zero credits.

Sub-100ms pickup from trigger to run.

Yes — a flow can be triggered by a broker topic, a webhook, and a schedule at the same time.

Turn your next event into a workflow

Model agentic workflows visually, trigger them from anywhere, and govern every run.