PushEngage
MessagingSend web push campaigns through PushEngage. Agents fire notifications to all subscribers or a targeted segment, pull subscriber counts, enrich profiles with custom attributes, remove subscribers, and inspect segments and drip campaigns.
What This Integration Enables
Web push is the bluntest instrument in the marketing stack: it appears on top of whatever the subscriber is doing, uninvited, with no inbox to soften it. Used precisely, that immediacy is the point, an order update or a restock alert that arrives the moment it matters. Used lazily, it is how sites train users to revoke permission. FlowRunner agents push the channel toward precision: they enrich subscriber profiles with behavioral attributes from the rest of the stack, size and target segments before sending, and put a person in front of every send that could interrupt thousands of screens. - Send immediate web push notifications, with optional hero image, to all subscribers or a targeted segment - Size audiences before launching, with total and per-segment subscriber counts - Enrich subscriber profiles with custom attributes for segmentation and personalization - Remove specific subscribers by device token when consent or accounts end - Inspect segments and drip campaigns to inform targeting decisions The channel's power to interrupt is exactly why FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate sits on the send path. The enrichment side deserves equal billing. A push subscriber base with no attributes can only ever be blasted; one where every purchase, survey answer, and site event lands as an attribute becomes a set of precise audiences. Because Add Subscriber Attributes overwrites keys it touches, FlowRunner agents write namespaced attribute keys per source, so the store's data never clobbers the survey's, and the segments built on both stay trustworthy.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Order events that arrive as pushes, not emails
An order fires in [Shopify](/integrations/shopify). The agent calls Add Subscriber Attributes to stamp the buyer's device token with the purchase, product line, order value, date, then sends an order-confirmation push with a deep link to the order page. Later, the shipped event does the same. The buyer gets updates on the surface they are already looking at, and the attributes written today become the segment targeted next month.
Interest signals become segment fuel
A [Typeform](/integrations/typeform) survey collects what subscribers care about. The agent matches respondents to their device tokens and writes their stated interests as attributes with Add Subscriber Attributes. PushEngage segments built on those attributes stop guessing: the next product announcement reaches the segment that asked for it, and Get Subscriber Count shows the audience growing as signals accumulate.
The audience report that runs itself
On a schedule, the agent pulls Get Subscriber Count for the site total and for each segment from List Segments, checks List Drip Campaigns for status changes, and appends the figures to [Google Sheets](/integrations/google-sheets) with a digest to [Slack](/integrations/slack). Subscriber growth, segment drift, and a drip campaign someone paused and forgot: all visible Monday morning without anyone opening the dashboard.
Human-in-Loop Highlight
Send Notification delivers via send_now, and its audience filter is optional: omit it and the notification goes to every subscriber the site has, immediately, on top of whatever each of them is doing. There is no unsend, and unlike email there is no inbox where a mistake sits quietly, a bad push physically interrupts thousands of people, and the ones it annoys revoke permission permanently, shrinking an audience that took years to build. So FlowRunner flows hard-code one rule: no send without a named audience the owner has seen. The agent always resolves the segment, always fetches the count, and posts the gate: "Restock push for the hiking line, segment outdoor-interest, 12,384 subscribers, copy and image attached. Send?" A missing or empty segment filter is treated as an error, never as "send to all." The same finality applies to Remove Subscriber, which permanently deletes a device token: agents propose removals from consent events, and a person confirms, because a deleted token cannot be re-subscribed by anyone but the user themselves.
Agent Capabilities
7 actionsNotifications
1- Send Notification Sends a web push immediately with title, message, click-through landing URL, optional hero image, and an audience filter such as a segment. The operation this page's human gate exists for.
Subscribers
4- List Subscribers Retrieves subscribers with pagination, optionally filtered by segment. The source of the device tokens every profile operation needs.
- Get Subscriber Count Returns the total or per-segment subscriber count. The sizing step that runs before every send, and the trend line that audience reporting is built on when captured over time.
- Add Subscriber Attributes Adds or updates custom key-value attributes on a subscriber by device token, overwriting existing keys. The enrichment write that turns anonymous tokens into targetable profiles.
- Remove Subscriber Permanently unsubscribes and removes a subscriber by device token. Cannot be undone, and human-confirmed in FlowRunner flows.
Segments
1- List Segments Retrieves the site's segments with names and subscriber counts. The targeting read behind every send decision.
Campaigns
1- List Drip Campaigns Retrieves the site's drip campaigns with name, status, and configuration. The audit read that keeps scheduled autoresponder sequences visible in reporting, so a paused welcome drip gets noticed in Monday's digest instead of three months into the quarter.
Frequently Asked Questions
What can FlowRunner do with PushEngage?
FlowRunner agents can run Send Notification, List Subscribers, and Get Subscriber Count in PushEngage, plus 4 more actions.
Does connecting PushEngage to FlowRunner require OAuth?
No. PushEngage connects to FlowRunner with an API key, no OAuth flow required.
Can PushEngage trigger a FlowRunner workflow automatically?
PushEngage doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with PushEngage
$100 in credits. No card required. Connect in minutes.