Gravitec

Send and track web push notifications with the Gravitec Server API, reaching everyone or a precise audience. Agents push time-sensitive alerts and read campaign performance back.

6 actions Basic auth available

Gravitec website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

A product that was marked out of stock returns to available in the store

Agent pulls the product name, price and landing URL for the restock

Agent resolves the audience from subscriber tags and confirms exactly one audience field is populated

Agent verifies the segment excludes subscribers already tagged as purchased

Agent posts the resolved segment and the drafted push copy into the growth channel

The growth owner confirms the segment, the agent calls Send Push Notification and then polls Get Campaign Stats for delivery, click and dismissal counts

What This Integration Enables

Gravitec is the connector in FlowRunner's catalog that talks to people who are not on your payroll. Every other push channel here reaches your own team on their own devices. A Gravitec web push lands on a customer's lock screen, from a browser permission they granted on your site and can revoke in one click. That changes what the connectors layer has to do: it is not enough to deliver the message, the agent has to be able to say who it went to and why.

The action set reflects that. Agents attach an alias to a browser subscription so a raw registration ID can be tied back to a real user record, add and remove tags so a subscriber's state moves as they buy, churn or upgrade, and target a send by tokens, aliases, tags or a tag segment. Delivery is asynchronous and Gravitec ships no outbound webhooks, so a send returns a campaign ID and the agent polls Get Campaign Stats to learn what actually happened. The dismissal counter is the honest one. It is the number that tells you a segment is tired of hearing from you, and it is the reason a person, not a schedule, should be the one to approve a broad send.

Without FlowRunner

Everyone gets everything Narrowing an audience takes longer than sending, so the restock alert goes to the whole list

Dismissals go unread Nobody notices that a segment is closing the notification rather than opening it

Consent treated as permanent A permission granted months ago is messaged at the same rate as one granted yesterday

With FlowRunner

Segment before send Every campaign resolves to a named tag segment that a person confirmed

Engagement read back Delivery, click and close counts land in the same place the send decision was made

Frequency held to the audience Tagging keeps recently messaged subscribers out of the next send

Use Case Scenarios

Back in stock, to the people who wanted it

A product returns to available in Shopify. The agent looks up the customers who had signed up for a restock alert on that item, resolves them to their push subscriptions through Get Subscriber Alias, and builds a tag segment that includes the interested tag and excludes anyone already tagged as purchased. It fires Send Push Notification against that segment with the product image and a direct link. Twenty minutes later it polls Get Campaign Stats and writes clicks and dismissals back to the campaign record. The alert reaches the shoppers who asked for it rather than every browser that ever accepted a prompt.

Publishing calendar with a scheduled push

An editorial team schedules a story in WordPress for the following morning. When the post is queued, the agent creates a matching Gravitec campaign with a future send time so the push lands at publication rather than at the moment the draft was saved. If the post is unscheduled or its headline changes before the send window, the agent flags the pending campaign to the editor instead of quietly delivering a headline nobody approved.

Keeping the subscriber record honest

Subscription state drifts. A person upgrades, cancels, or unsubscribes in one system and the push tags never hear about it. On a schedule, the agent walks the customer records in PostgreSQL, calls Get Subscriber Alias to confirm each subscription is still an active follower, and reconciles the difference with Add Subscriber Tag and Remove Subscriber Tag. Subscriptions that no longer resolve are reported as an exception rather than silently retargeted, because a subscription that disappeared is usually a person who left.

Human-in-Loop Highlight

Send Push Notification takes exactly one audience field, and leaving every audience field empty is not an error. It means everyone. That single empty-field case is the irreversible operation on this connector: a web push cannot be recalled, it arrives on a stranger's phone, and the cost of getting it wrong is not a retry, it is the permission itself. So when a flow resolves to an empty audience, or to a tag segment larger than the ceiling the team set, the agent stops and posts the case into the growth channel: "This restock push resolves to every subscriber on the site, not the 2,300 who asked about this product. The tag segment I built is attached. Send to the segment, send to everyone, or hold?" A person answers, and only then does the campaign ID come back. This is human-in-the-loop applied where it belongs, at the boundary between an audience you selected and an audience you defaulted into.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

6 actions

Campaigns

Send Push Notification Sends a web push notification to subscribers, immediately or scheduled for a future time. Returns a campaign ID straight away because delivery is asynchronous. Used as the send step once the audience has been resolved to a specific token list, alias, tag or tag segment.
Get Campaign Stats Returns how many devices a campaign was sent to, how many received it, how many clicked and how many dismissed it. Gravitec publishes no delivery webhook, so agents poll this after a send to follow a campaign to completion and to feed dismissal rates back into targeting decisions.

Subscribers

Set Subscriber Alias Attaches a human readable alias to a push subscriber so later sends can target them by name instead of by an opaque registration ID. Used to bind a browser subscription to a user record in a CRM or application database.
Get Subscriber Alias Looks up a subscriber by registration ID and reports whether they exist, whether they are still an active follower, and what alias is attached. Used as the verification step before spending a send on a subscription that may already be gone.
Add Subscriber Tag Tags a subscriber so they are included in targeted sends. Used to move a subscriber's state as they buy, upgrade or churn, so the audience for the next campaign builds itself.
Remove Subscriber Tag Removes a tag so the subscriber drops out of sends targeting it. Used for suppression: a customer who just purchased comes out of the promotion segment before the next campaign runs.

Frequently Asked Questions

What can FlowRunner do with Gravitec?

FlowRunner agents can run Send Push Notification, Get Campaign Stats, and Set Subscriber Alias in Gravitec, plus 3 more actions.

Does connecting Gravitec to FlowRunner require OAuth?

No. Gravitec connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Gravitec trigger a FlowRunner workflow automatically?

Gravitec doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Gravitec

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us