Pushinator
for LuumenAI
Read your push channels, then send alerts as an approved step
Pushinator holds the push channels your team uses to reach on-call engineers and subscribed devices. Connect it and Luumen can list those channels, read one channel's details, and confirm which account the API key belongs to. Sending a notification or changing a channel is previewed first, then runs as an approved, audited step.
The Pushinator toolbox
7 tools: 3 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet ChannelGet one Pushinator notification channel by its channel ID.
- ReadGet Current UserReturn the Pushinator user associated with the connected API key.
- ReadList ChannelsList every notification channel belonging to the connected Pushinator account.
- WriteCreate ChannelCreate a Pushinator notification channel and return its channel ID and properties. Approval by default
- WriteDelete ChannelPermanently delete a Pushinator notification channel by ID. Approval by default
- WriteSend NotificationSend a push notification immediately to all subscribers of a Pushinator channel. Approval by default
- WriteUpdate ChannelReplace the editable name and optional description of an existing Pushinator notification channel. Approval by default
One prompt, start to finish
What a governed Pushinator 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 — create channel, delete channel, send notification, update channel — is shown as a plan and requires approval by default, including the 2 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 Pushinator — 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 Pushinator to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.