Skip to main content
You connect Pushover once at the MSP level. Neo needs the API token of a Pushover application. To add or remove team members, it also needs your team’s API token.

1. Create the application

Sign in at pushover.net and open Create an Application/API Token (pushover.net/apps/build). Name it “Neo”, accept the terms and click Create Application. Copy the API Token/Key it shows: 30 letters and digits. If you use Pushover for Teams, create the application under your team, so its messages count against the team’s quota and it can manage the team’s delivery groups.

2. Find the team API token (optional)

Only needed for the Teams API: adding a technician to your team, removing one, or revoking an invitation. A team administrator copies the Team API Token from the team’s page at pushover.net/teams. Delivery groups, such as an on-call group, work with the application token alone.

3. Add the tokens in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the Pushover card, under Chat & Alerting.
2

Save the tokens

Paste the application API token, and the team API token if you have one, and click Save settings. Neo checks each token against Pushover before saving, so a wrong token is rejected straight away.

4. Turn Pushover on per agent

Open the agent, go to the Integrations section, and pick an access profile for the Pushover block, or set each area yourself: The agent also needs its PSA permissions to add internal notes on tickets, and to change a ticket’s priority or owner when your instructions ask for that. Tell the agent in its instructions which user or group key to page, or the name of the on-call delivery group.
Pushover allows 10,000 messages a month per account, 25,000 for a team. A message sent to a group counts once per member. When the quota is spent, Pushover refuses messages until the next month, and Neo tells you so.