> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Pushover

The Pushover connector lets your AI agent act in each user's Pushover account. Each user connects their own Pushover API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 18 tools.

**Authentication:** API Key
**Categories:** Communication, Monitoring
**Tools:** 18: 7 read, 10 write, 1 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=PUSHOVER)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Pushover connection

   In **AgentKit > Connections**, create a Pushover connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'pushover'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Pushover:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'pushover_app_limits_get',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "pushover"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Pushover:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="pushover_app_limits_get",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Pushover credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'pushover_app_limits_get',
  toolInput: {},
  connector: 'pushover',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="pushover_app_limits_get",
    tool_input={},
    connection_name="pushover",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `pushover_app_limits_get`

Get Message Limits · Read-only

Get the account's monthly message limit, the number of messages sent this month and when the count resets.
Returns limit, remaining and reset (Unix timestamp).
Use pushover_app_limits_get before bulk sends to avoid 429 errors.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `pushover_group_get`

Get Delivery Group · Read-only

Get a delivery group's name and members.
Returns the name and each member's user key, device, memo and disabled flag.
Use pushover_group_get to see who receives a group's messages.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `group_key` (`string`, required): Delivery group key, from pushover_groups_list or pushover_group_create. Example: go4abk17j3itsva6thz99mdudgq2gm

Example input: `{"group_key":"<group_key>"}`

### `pushover_groups_list`

List Delivery Groups · Read-only

List the account's delivery groups.
Returns each group's key and name.
Use pushover_groups_list to find a group key. Send to a group by passing its key as user in pushover_message_send.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `pushover_licenses_credits_get`

Get License Credits · Read-only

Get the number of prepaid Pushover license credits left on the account.
Returns credits.
Use pushover_licenses_credits_get before pushover_license_assign.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `pushover_receipt_get`

Get Receipt · Read-only

Get the status of an emergency-priority message by its receipt; poll no more than once every 5 seconds, for up to a week.
Returns acknowledged, acknowledged_at and _by, last_delivered_at, expired, expires_at and callback status.
Use pushover_receipt_get to see whether someone acknowledged an alert. Use pushover_receipt_cancel to stop its repeats.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `receipt` (`string`, required): Receipt ID returned when an emergency-priority (priority 2) message was sent. Example: rLqVuqTRh62UzxtmqiaLzQmVcPgiCy

Example input: `{"receipt":"<receipt>"}`

### `pushover_sounds_list`

List Sounds · Read-only

List the notification sounds available to the application, including custom sounds uploaded to the account.
Returns a map of sound IDs to display names.
Use pushover_sounds_list to pick a sound for pushover_message_send.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `pushover_user_validate`

Validate User · Read-only

Check that a user or group key is valid and has at least one active device (or the named device).
Returns status 1 with the user's active device names and licensed platforms, or status 0 with the problem.
Use pushover_user_validate when collecting a user key, before sending to it.

Read only: yes. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `user` (`string`, required): Recipient's Pushover user key or a delivery group key (30 characters, from the user's dashboard). Example: uQiRzpo4DXghDmr9QzzfQu27cmVRsG
- `device` (`string`, optional): Device name to validate as well. Example: iphone

Example input: `{"user":"<user>"}`

### `pushover_glance_update`

Update Glance · Write

Update the data shown on a user's Pushover widget (Apple Watch complication) without sending a notification; fields not sent keep their value and an empty string clears one. Updates can take up to 10 minutes to appear.
Returns status 1.
Use pushover_glance_update for a live number or status on a watch. Use pushover_message_send for alerts.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `user` (`string`, required): Recipient's Pushover user key or a delivery group key (30 characters, from the user's dashboard). Example: uQiRzpo4DXghDmr9QzzfQu27cmVRsG
- `count` (`integer`, optional): A number for small screens; may be negative. Example: 1204
- `device` (`string`, optional): Device name to send to only that device (comma-separate several); leave empty for all of the user's devices. Example: iphone
- `percent` (`integer`, optional): 0 to 100, shown as a progress ring. Example: 64
- `subtext` (`string`, optional): Second line, up to 100 characters. Example: +12% vs yesterday
- `text` (`string`, optional): Main line, up to 100 characters. Example: 1,204 today
- `title` (`string`, optional): Description of the data, up to 100 characters. Example: Widgets sold

Example input: `{"user":"<user>"}`

### `pushover_group_create`

Create Delivery Group · Write

Create a delivery group.
Returns the new group key.
Use pushover_group_create to broadcast to several users with one key, then add members with pushover_group_user_add.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Group name, unique in the account. Example: On-call engineers

Example input: `{"name":"<name>"}`

### `pushover_group_rename`

Rename Delivery Group · Write

Rename a delivery group.
Returns status 1.
Use pushover_group_rename to change a group's name.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `group_key` (`string`, required): Delivery group key, from pushover_groups_list or pushover_group_create. Example: go4abk17j3itsva6thz99mdudgq2gm
- `name` (`string`, required): New group name, unique in the account. Example: Primary on-call

Example input: `{"group_key":"<group_key>","name":"<name>"}`

### `pushover_group_user_add`

Add Group Member · Write

Add a Pushover user to a delivery group.
Returns status 1.
Use pushover_group_user_add to add someone to a broadcast group. Use pushover_group_user_remove to take them out.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `group_key` (`string`, required): Delivery group key, from pushover_groups_list or pushover_group_create. Example: go4abk17j3itsva6thz99mdudgq2gm
- `user` (`string`, required): The member's Pushover user key. Example: uQiRzpo4DXghDmr9QzzfQu27cmVRsG
- `device` (`string`, optional): Restrict the member's messages to this device. Example: iphone
- `memo` (`string`, optional): Free-text note about the member, such as their name (up to 200 characters). Example: Jim (SRE)

Example input: `{"group_key":"<group_key>","user":"<user>"}`

### `pushover_group_user_disable`

Disable Group Member · Write

Temporarily stop sending a group's messages to one member.
Returns status 1.
Use pushover_group_user_disable for someone going off call. Use pushover_group_user_enable to resume.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `group_key` (`string`, required): Delivery group key, from pushover_groups_list or pushover_group_create. Example: go4abk17j3itsva6thz99mdudgq2gm
- `user` (`string`, required): The member's Pushover user key. Example: uQiRzpo4DXghDmr9QzzfQu27cmVRsG
- `device` (`string`, optional): Only disable the membership for this device. Example: iphone

Example input: `{"group_key":"<group_key>","user":"<user>"}`

### `pushover_group_user_enable`

Enable Group Member · Write

Resume sending a group's messages to a disabled member.
Returns status 1.
Use pushover_group_user_enable to undo pushover_group_user_disable.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `group_key` (`string`, required): Delivery group key, from pushover_groups_list or pushover_group_create. Example: go4abk17j3itsva6thz99mdudgq2gm
- `user` (`string`, required): The member's Pushover user key. Example: uQiRzpo4DXghDmr9QzzfQu27cmVRsG
- `device` (`string`, optional): Only enable the membership for this device. Example: iphone

Example input: `{"group_key":"<group_key>","user":"<user>"}`

### `pushover_license_assign`

Assign License · Write

Assign one prepaid Pushover license to a user by user key or email, optionally for one platform; uses one license credit.
Returns status 1 and the remaining credits.
Use pushover_license_assign to give your users Pushover without them paying. Check credits with pushover_licenses_credits_get.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, optional): The user's email, which creates an account if needed; give this or user. Example: jane@example.com
- `os` (`string`, optional): Platform to license: Android, iOS or Desktop; leave empty for the first platform the user registers. One of: Android, iOS, Desktop. Example: iOS. One of: `Android`, `iOS`, `Desktop`.
- `user` (`string`, optional): The user's Pushover user key; give this or email. Example: uQiRzpo4DXghDmr9QzzfQu27cmVRsG

Example input: `{}`

### `pushover_message_send`

Send Notification · Write

Send a push notification to a Pushover user or delivery group, with optional title, link, priority, sound, HTML, image and expiry. Messages are limited to 1024 characters; each successful send counts against the account's monthly quota.
Returns status 1 and a request ID, plus a receipt for emergency-priority messages.
Use pushover_message_send to alert someone's phone or desktop. Use pushover_receipt_get to check whether an emergency message was acknowledged.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `message` (`string`, required): Message body, up to 1024 characters; set html to 1 to allow basic HTML. Example: Backup of database "example" finished in 16 minutes.
- `user` (`string`, required): Recipient's Pushover user key or a delivery group key (30 characters, from the user's dashboard). Example: uQiRzpo4DXghDmr9QzzfQu27cmVRsG
- `attachment_base64` (`string`, optional): Image attachment as base64 (up to 5 MB); set attachment_type too. Example: iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mP8z8BQDwAEhQGAhKmMIQAAAABJRU5ErkJggg==
- `attachment_type` (`string`, optional): MIME type of attachment_base64, such as image/jpeg or image/png. Example: image/png
- `callback` (`string`, optional): For priority 2: URL Pushover POSTs to when the message is acknowledged. Example: https://example.com/pushover/ack
- `device` (`string`, optional): Device name to send to only that device (comma-separate several); leave empty for all of the user's devices. Example: iphone
- `expire` (`integer`, optional): For priority 2: seconds to keep repeating, at most 10800. Example: 3600
- `html` (`integer`, optional): 1 to enable HTML formatting. One of: 0, 1. Example: 1. One of: `0`, `1`.
- `monospace` (`integer`, optional): 1 to show the message in a monospace font (not with html). One of: 0, 1. Example: 0. One of: `0`, `1`.
- `priority` (`integer`, optional): -2 (no alert), -1 (quiet), 0 (default), 1 (high, bypasses quiet hours) or 2 (emergency, repeats until acknowledged; needs retry and expire). One of: -2, -1, 0, 1, 2. Example: 0. One of: `-2`, `-1`, `0`, `1`, `2`.
- `retry` (`integer`, optional): For priority 2: seconds between repeats, at least 30. Example: 60
- `sound` (`string`, optional): Sound name from pushover_sounds_list, overriding the user's default. Example: magic
- `tags` (`string`, optional): For priority 2: comma-separated tags for cancelling with pushover_receipts_cancel_by_tag. Example: server=mail01,dc=chicago
- `timestamp` (`integer`, optional): Unix timestamp to show instead of the time Pushover received the message. Example: 1763280000
- `title` (`string`, optional): Title, up to 250 characters; defaults to the app's name. Example: Backup finished - SQL1
- `ttl` (`integer`, optional): Seconds after which the message is deleted from devices (ignored for priority 2). Example: 3600
- `url` (`string`, optional): Supplementary URL shown under the message, up to 512 characters. Example: https://status.example.com/incidents/42
- `url_title` (`string`, optional): Title for the supplementary URL, up to 100 characters. Example: View incident

Example input: `{"message":"<message>","user":"<user>"}`

### `pushover_receipt_cancel`

Cancel Emergency Retries · Write

Stop the repeats of an emergency-priority message before it expires.
Returns status 1.
Use pushover_receipt_cancel when the issue is resolved. Use pushover_receipts_cancel_by_tag to cancel many messages at once.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `receipt` (`string`, required): Receipt ID returned when an emergency-priority (priority 2) message was sent. Example: rLqVuqTRh62UzxtmqiaLzQmVcPgiCy

Example input: `{"receipt":"<receipt>"}`

### `pushover_receipts_cancel_by_tag`

Cancel Emergency Retries by Tag · Write

Stop the repeats of every active emergency-priority message sent by the application with a given tag.
Returns status 1 and the number of messages cancelled.
Use pushover_receipts_cancel_by_tag to clear a batch of related alerts, such as all alerts for one datacenter.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `tag` (`string`, required): Tag the messages were sent with. Example: dc=chicago

Example input: `{"tag":"<tag>"}`

### `pushover_group_user_remove`

Remove Group Member · Destructive

Remove a user from a delivery group.
Returns status 1.
Use pushover_group_user_remove to take someone out. Use pushover_group_user_disable to pause them instead.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `group_key` (`string`, required): Delivery group key, from pushover_groups_list or pushover_group_create. Example: go4abk17j3itsva6thz99mdudgq2gm
- `user` (`string`, required): The member's Pushover user key. Example: uQiRzpo4DXghDmr9QzzfQu27cmVRsG
- `device` (`string`, optional): Only remove the membership for this device. Example: iphone

Example input: `{"group_key":"<group_key>","user":"<user>"}`

## Related

Other Communication connectors ([all 132](/agentkit/connectors/?category=communication)):

- [Gmail](/agentkit/connectors/gmail/): Scalekit connector, OAuth, 48 tools
- [Slack](/agentkit/connectors/slack/): Scalekit connector, OAuth, 96 tools
- [Google Calendar](/agentkit/connectors/googlecalendar/): Scalekit connector, OAuth, 30 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
