PushAlert
for LuumenAI
Read push stats and segments, then send or reshape them with approval
Connect PushAlert and Luumen can read your Web Push setup on request: segment names and subscriber counts, custom attributes on a single subscriber, and delivery, click, and click-through numbers for a notification you already sent. Changes — creating a segment, moving subscribers, setting attributes, sending a push — are previewed and, by default, held for your approval.
The PushAlert toolbox
9 tools: 3 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Notification StatsGet attempted, delivered, clicked, and click-through-rate statistics for a Web Push notification.
- ReadGet Subscriber AttributesGet custom attributes for a Web Push subscriber.
- ReadList SegmentsList all Web Push subscriber segments and their subscriber counts.
- WriteAdd Subscribers to SegmentAdd one or more Web Push subscribers to an existing segment. Approval by default
- WriteCreate SegmentCreate a Web Push subscriber segment with a letters-and-digits name. Approval by default
- WriteDelete SegmentPermanently delete a Web Push subscriber segment by ID. Approval by default
- WriteRemove Subscribers from SegmentRemove one or more Web Push subscribers from an existing segment. Approval by default
- WriteSend Web Push NotificationSend an irreversible Web Push notification to a saved segment, explicit subscriber IDs, or attribute-matched subscribers. Approval by default
- WriteSet Subscriber AttributesAdd or update custom attributes for a Web Push subscriber. Approval by default
One prompt, start to finish
What a governed PushAlert 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.
This connection exposes write actions such as add subscribers to segment, create segment, delete segment, remove subscribers from segment, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 PushAlert — 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 PushAlert to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.