Requirements
Pushover requires an active account and an API access token from your account settings to connect — both are set up on its own site.[3]
Get your Pushover credentials
- Access TokenpasswordRequired
Your application's API token. Register an application (free) at pushover.net/apps/build, set its name and icon, and Pushover will generate an API token (also called APP_TOKEN). Tokens are case-sensitive, 30 characters long. Paste that token here.
[1]
Connect Pushover in WEXTL
- Log in to your WEXTL account, add the Pushover node module to your workflow, and click Create new credential.
- Optional: In the Credential name field, enter a name for the credential.
- Enter the authentication credentials you copied from your Pushover account, or follow the on-screen instructions to create the credential.
- If prompted, authenticate your account and confirm access.
- If you want to make changes to your credential in the future, follow the steps in Manage credentials →
Notes
Credentials are org-scoped; share them with teammates from the Credentials picker on any of its nodes.For detailed information on connecting an application, see Connect an application →
Pushover node modules
The list below is a reference of every Pushover node module the integration supports. You will be able to pick any of them on the workflow canvas while building automations.
Browse every Pushover node module below — each one opens to show its input parameters, outputs, and connection requirements.
| Field | Type |
|---|---|
Session SecretRequired | secret |
Device IDRequired | text |
Limit | number |
| Field | Type |
|---|---|
Message ID | text |
Message ID | text |
Message | text |
App | text |
App ID | text |
App ID | text |
Icon | text |
Date | date |
Queued Date | date |
Dispatched Date | date |
Priority | number |
Acknowledged | number |
UMID | text |
UMID | text |
Title | text |
Sound | text |
URL | url |
URL Title | text |
Receipt | text |
HTML | text |
| Field | Type |
|---|---|
Status | number |
Request ID | text |
Message Limit | number |
Remaining | number |
Reset (Unix timestamp) | number |
| Field | Type |
|---|---|
Status | number |
Request ID | text |
Sounds | object |
| Field | Type |
|---|---|
Status | number |
Credits Remaining | number |
Request ID | text |
| Field | Type |
|---|---|
User / Group KeyRequired | choice |
MessageRequired | text |
Title | text |
Device | text |
HTML | choice |
Monospace | choice |
Priority | choice |
Sound | choice |
Timestamp | number |
Time To Live (seconds) | number |
Supplementary URL | text |
URL Title | text |
Retry (seconds) | number |
Expire (seconds) | number |
Callback URL | text |
Tags | text |
Encrypted | choice |
Attachment (binary) | text |
Attachment Filename | text |
Attachment (Base64) | text |
| Field | Type |
|---|---|
Status | number |
Request ID | text |
Receipt | text |
Templates
Look for Pushover templates in the WEXTL template library.
Browse templates →Explore alternative apps
- AWS SQS[2]Send, receive, and manage messages on Amazon SQS queues.
- AWS SESSend transactional email and manage Amazon SES identities, templates, contacts, suppressions, and configuration sets.
- BatchDialerCloud predictive dialer for sales and collections teams with contacts and campaigns.
- Benchmark EmailEmail marketing platform for campaigns, lists, automations, and subscriber engagement.
- CallbellShared inbox for WhatsApp, Messenger, Instagram, and Telegram support.
References
- WEXTL® Pushover Source Code connector implementation.
- Our users use cases and automations.
- Official API Documentation for Pushover.
- WEXTL® visual workflow builder data.
Last updated: Sep 8, 2026 15:22