# Pushover integrations: messages and receipts

> Send a message in Pushover. Connect Pushover to the rest of your communication stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/pushover-integrations/
**Categories:** Communication
**Connects through:** HTTP Connector

## Overview

Pushover sends real-time notifications from apps, servers, and scripts to phones, tablets, and desktops, with delivery groups for teams. Tray.ai connects to Pushover through the HTTP Connector, so your workflows can call the Pushover API alongside the rest of your stack.

## Use cases

### Messages

Read and create messages in Pushover from any Tray.ai workflow. The Pushover API covers calls such as send a message and check message limits.

- Send a message
- Check message limits
- List notification sounds

### Users

Read users in Pushover from any Tray.ai workflow. The Pushover API covers calls such as validate a user key and validate a group key.

- Validate a user key
- Validate a group key

### Groups

Read, create, update, and delete groups in Pushover from any Tray.ai workflow. The Pushover API covers calls such as create a group and get a group.

- Create a group
- Get a group
- Add a user

### Receipts

Read and delete receipts in Pushover from any Tray.ai workflow. The Pushover API covers calls such as get a receipt and cancel by tag.

- Get a receipt
- Cancel by tag

### Teams

Read, create, and delete teams in Pushover from any Tray.ai workflow. The Pushover API covers calls such as get a team and add a team user.

- Get a team
- Add a team user
- Remove a team user

## Challenges Tray.ai solves

### Keeping Pushover credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Pushover credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Pushover API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Pushover API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Pushover?

Yes. Tray.ai connects to Pushover through the HTTP Connector, which calls the Pushover API directly. Any call the Pushover API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Pushover?

The Pushover API uses an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Pushover connector?

Pushover runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Pushover connector from the Pushover API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/