Pushover
for LuumenAI
Check delivery groups and alert receipts, then change who gets paged
Pushover is where your on-call alerts land. Luumen reads it directly: which delivery groups exist, who is in them, whether an emergency-priority message was acknowledged, and how many messages your app has left this month. Changes to groups and retries run as previewed steps you approve first. Luumen connects with an API key.
The Pushover toolbox
29 tools: 13 read, 16 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadFetch Pending MessagesDownload pending messages for a registered device.
- ReadClient Realtime WebSocket ConnectionEstablish a secure WebSocket connection for real-time message notifications.
- ReadGet Application Icon ImageFetch an application icon PNG by icon identifier.
- ReadGet App LimitsRetrieve the current monthly message limit, remaining messages, and reset time for a Pushover application.
- ReadGet Application TokenFetch stored Pushover application API token.
- ReadGet Receipt StatusPoll the status of an emergency-priority notification receipt.
- ReadGet Team API TokenFetch stored Pushover for Teams API token.
- ReadGet Group DetailsRetrieve details for a Delivery Group.
- ReadList Delivery GroupsList all Delivery Groups.
- ReadCheck License CreditsRetrieve remaining license credits for a Pushover application.
- ReadStore Team API TokenSecurely store a Pushover for Teams API token.
- ReadSubscription FlowValidate and return a Pushover subscription code.
- ReadValidate User or GroupValidate a Pushover user or group key for deliverability.
- WriteCancel Receipt RetriesCancel further retries for an emergency-priority message before its expiry. Approval by default
- WriteCancel Retries by TagCancel retries for all active emergency-priority Pushover messages matching a specific tag. Approval by default
- WriteClient Acknowledge Delete Up To IDDelete/acknowledge device messages up to a specific message ID. Approval by default
- WritePushover Client LoginAuthenticate a Pushover user by email and password. Approval by default
- WriteRegister Open Client DeviceRegister an Open Client desktop device. Approval by default
- WriteGlances UpdateUpdate a user's Glances widget data without sending a notification. Approval by default
- WriteAdd User to GroupAdd an existing Pushover user to a delivery group. Approval by default
- WriteCreate GroupCreate a new Delivery Group. Approval by default
- WriteDisable Group UserTemporarily disable deliveries to a user or specific device within a Pushover group. Approval by default
- WriteGroup Enable UserRe-enable deliveries to a previously disabled user (or specific device) within a Pushover group. Approval by default
- WriteRemove User from GroupRemove a user (or optionally a specific device) from a Pushover delivery group. Approval by default
- WriteRename Delivery GroupRename an existing Delivery Group. Approval by default
- WriteAssign LicenseAssign a pre-paid license credit to a Pushover user by key or email. Approval by default
- WriteSend MessageSend a push notification with optional title, URL, priority, sound, attachments, and filters. Approval by default
- WriteAdd Team UserAdd a user to a Pushover for Teams organization. Approval by default
- WriteRemove User from TeamRemove a user from a Pushover for Teams organization. Approval by default
One prompt, start to finish
What a governed Pushover 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 — cancel receipt retries, cancel retries by tag, client acknowledge delete up to id, pushover client login, and more — is shown as a plan and requires approval by default, including the 5 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 Pushover — 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 Pushover to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.