Webpushr
for LuumenAI
Check subscriber reach and campaign delivery, then send push as an approved step
Connect Webpushr and your team can ask how many subscribers are active right now, or how a campaign that went out this morning is actually being delivered and clicked. Sending is a separate step: Luumen shows the audience, title, and body first, and waits for your approval by default before the campaign is created.
The Webpushr toolbox
6 tools: 2 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Notification StatusGet delivery and engagement counts for a Webpushr notification campaign using its campaign ID.
- ReadGet Subscriber CountReturn lifetime and currently active subscriber counts for the connected Webpushr site.
- WriteSend Notification to All SubscribersCreate or schedule a push notification campaign for every subscriber of the connected Webpushr site. Approval by default
- WriteSend Notification by AttributesCreate or schedule a push notification campaign for subscribers matching any supplied custom attribute key/value pair. Approval by default
- WriteSend Notification to SegmentsCreate or schedule a push notification campaign for subscribers in one or more Webpushr segments. Approval by default
- WriteSend Notification to SubscriberSend or schedule a push notification to one Webpushr subscriber ID. Approval by default
One prompt, start to finish
What a governed Webpushr run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — send notification to all subscribers, send notification by attributes, send notification to segments, send notification to subscriber — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Webpushr — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut Webpushr to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.