Pushwoosh

What This Integration Enables

A push notification is the most interruptive message a company can send: it lights up a lock screen, and users answer bad targeting with the app's notification permissions or the app itself. Pushwoosh gives you the machinery, messages, scheduling, device registry, tags, and FlowRunner supplies the operating discipline. Agents keep device tags synchronized with what users actually do, so the segmentation filters behind every campaign describe the present, not the install date. They schedule sends, hold the message codes, verify delivery, and keep the cancel path live until the send moment passes. - Send or schedule pushes to an application, targeted by saved audience filters - Cancel scheduled messages and inspect delivery status of sent ones - Register and unregister devices from your own backend systems - Set custom tags per device, City, Level, Premium, to power segmentation - Tie push campaigns to real events flowing through the rest of your stack Scheduling is the quiet superpower in this loop. Because Create Message accepts a future send date and returns a cancellable message code, agents can queue pushes at the moment an event happens while targeting the moment a user will actually welcome them, and keep the option to cancel open until the window arrives. Event-time logic, send-time delivery, revocable in between. Because a push cannot be recalled once delivered, FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate reviews the audience before the schedule, not after the complaint. Transactional single-device pushes run free; filtered campaigns earn a human look at exactly one thing, whether the filter's reach matches the author's intent.