Validate and Notify a Recipient
Send [message] with title [title] to Pushover recipient [recipient key]. Check the recipient before sending.
Leina connects to Pushover to help you send phone alerts, check emergency acknowledgments, and review message limits. Ask in your team chat. Leina does the work and brings back the result.
Connect Pushover, choose what to share, and hand off your first task.
You
Send “The staging backup is ready for review” to my Pushover recipient [recipient key], titled “Backup ready”.
Leina
Pushover accepted the notification for the selected recipient.
Pushover · Notification submitted
Backup ready
The requested message is queued for the selected recipient.
A Pushover AI agent sends the alerts you request to selected recipients and checks acknowledgments for emergency notifications.
You specify the source and the destination. Leina uses the content available to your connection and returns the result for you to review.
Pushover delivers application notifications to phones and other supported devices.
Provide the recipient key and message.
Validate that the recipient can receive notifications.
Submit the message and report acceptance.
Copy a prompt, add your details, and send it to Leina in your connected team chat.
Send [message] with title [title] to Pushover recipient [recipient key]. Check the recipient before sending.
Check emergency notification [receipt identifier] and tell me whether it was acknowledged or expired.
Review my Pushover notification allowance and tell me how much remains and when it resets.
Your next Pushover task can start with a message.
Tell Leina what you need in your team chat. Include the source, destination, and expected result.
Connect the tools involved and give Leina access to the content it needs.
Share the source material, say where the result belongs, and describe what you need.
Review the result and any changes in the connected app.
Hand off these everyday tasks to your AI employee.
Send a Pushover notification to a user or delivery group, with optional emergency settings, URL metadata, and image attachment.
Validate that a Pushover user or delivery group key can receive notifications, optionally restricted to one device.
Get the current monthly message limit, remaining messages, and reset time for the connected Pushover application.
Return the application API token resolved from the action input or the connected credential.
Return the Team API token resolved from the action input or the connected credential metadata.
Validate a Pushover Team API token for later use. Persist the token through the provider connection extra field when needed.
Download a Pushover application icon PNG by icon identifier and return its binary content as base64.
Get the status of an emergency notification receipt, including acknowledgment, callback, and expiry details.
Cancel further retries for one emergency receipt before it expires.
Cancel retries for all active emergency receipts that share the provided tag.
Update Pushover Glances widget data for a user without creating a push notification.
Create a new Pushover delivery group.
List the delivery groups owned by the connected Pushover application account.
Get the name and membership of a Pushover delivery group.
Add an existing Pushover user to a delivery group.
Remove a user, or one of the user's devices, from a delivery group.
Temporarily disable deliveries to a user, or one of the user's devices, inside a delivery group.
Re-enable deliveries to a previously disabled user, or one of the user's devices, inside a delivery group.
Rename an existing Pushover delivery group.
Assign one prepaid Pushover license credit to a user by key or email address.
Get the number of prepaid Pushover license credits remaining on the application.
Validate and echo a Pushover subscription code collected through the web subscription flow.
Add a user to a Pushover for Teams organization using the Team API token.
Remove a user from a Pushover for Teams organization without deleting the user's Pushover account.
Authenticate an Open Client user with email, password, and optional two-factor code.
Register an Open Client desktop device using a user session secret.
Download pending Open Client messages for a registered device.
Acknowledge and delete all Open Client messages up to the provided message identifier.
Open a temporary Open Client WebSocket session, login with the provided device and secret, and collect realtime events until timeout or close.
Connect the Apps your work depends on, and give Leina the context to carry the task forward.
Hand off a task while your team is discussing it. Leina uses your connected tools and brings the result back to the conversation.
See How Leina Works in SlackPushover accepted the notification for the selected recipient.
No. Ordinary notification acceptance does not confirm reading. Emergency notifications provide a separate acknowledgment receipt.
A connected application, the recipient’s user or group key, and the message. Emergency alerts also need a repeat interval and expiry time.
Start with one task you already need to do. Tell Leina what a finished result should look like.
Connect Pushover, choose what to share, and hand off your first task.