Push, IoT & Real-Time Notifications
Last-mile delivery from workflows: mobile push (FCM), browser push (your VAPID keys), MQTT for devices, WebSocket for live apps.
The notify action does last-mile delivery to devices and apps — the part most automation tools stop short of. Four adapters: FCM for mobile app notifications, Web Push for browsers using your own VAPID keys, MQTT for IoT devices subscribed to your broker topics, and WebSocket for pushing into live applications. A survey response really can flip a device.
Workflow triggers
Any workflow trigger
Push is an action — pair it with any trigger: survey responses, thresholds, schedules, inbound events.
Workflow actions
FCM app push
Notify your mobile app's users from workflow records.
Web Push
Browser notifications signed with your own VAPID keys — your subscription list stays yours.
MQTT publish
Publish to a topic on your broker; subscribed IoT devices react.
WebSocket push
Deliver events into live apps over a socket endpoint.
How data flows
Outbound last-mile delivery with variable insertion from workflow records and idempotency-wrapped dispatch, so retries never double-notify.
Connection: Per-transport connections: FCM credentials for app push, your VAPID key pair for Web Push, your MQTT broker and topic, or a WebSocket endpoint URL. Each connection has a delivery test.
Worked example: A kiosk that reacts to feedback
Trigger: a low CSAT score arrives from the on-site kiosk survey.
Action: an MQTT message publishes to the site's alerts topic — the duty manager's device buzzes.
Action: the ops dashboard updates instantly over WebSocket.
The follow-up task and re-survey run as normal workflow steps.
Setting it up
1.
Create a notify connection and pick the transport (FCM, Web Push, MQTT, WebSocket).
2.
Provide that transport's credentials or endpoint.
3.
Run the delivery test, then add the notify action to a workflow.
Frequently asked questions
Can a survey response really reach an IoT device?
Yes — the MQTT adapter publishes to a topic on your broker; any subscribed device reacts. Ceiling lights that blush at bad NPS are technically within reach.
Who owns the Web Push subscriptions?
You do — pushes are signed with your own VAPID key pair.
Is delivery reliable?
Dispatch is idempotency-wrapped (retries replay, never double-send) and every connection has a test endpoint.