Pushbullet integration

Pushbullet pushes alerts to every device signed into your Pushbullet account. Each alert is a note push: a title carrying the monitor and its new status, and a body with the detail. Outages and recoveries arrive the same way, since Pushbullet has no priority.

What you need

An access token from your Pushbullet account.

In Pushbullet, go to Settings → Account.
Create Access Token.
Copy the token.

Connect it

In the dashboard, go to Manage → Integrations and click the Pushbullet card. Give it a name, paste the token into Access Token and click Add integration.

Or through the API, with POST /integration/pushbullet:

curl -X POST https://api.siteqwality.com/integration/pushbullet \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "friendly_name": "My devices",
    "access_token": "<pushbullet-access-token>"
  }'

Both fields are required. The token is not verified against Pushbullet at save time, and it never reads back in full.

Add it to a notification group

Right after you add the integration, the dashboard offers to do this for you: choose a group or create one, choose which monitors alert that group (the ones that already do, every monitor, or ones you pick), then send a test. If you skipped it, Route alerts on the integration’s card opens the same step. To do it by hand:

Go to Respond → Notifications. Click a group’s name to open it, or click Add group to make a new one.
Under Notifications, click Add notification method. Set Notification type to Pushbullet and choose this integration under Integration.
Click Done editing, then Save changes (Create group for a new group).

Through the API, create the channel with POST /notification:

curl -X POST https://api.siteqwality.com/notification \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "notification_group_id": "<your-group-id>",
    "type": "pushbullet",
    "details": { "pushbullet_integration_id": "<pushbullet-integration-id>" }
  }'

Delivery behavior

A send is attempted once, and a refusal from Pushbullet is recorded as rejected. Any other failure is run up to two more times, so a duplicate push is possible. If those runs fail too, the alert is dropped with no record in alert history. See delivery guarantees.

Limitations

Heartbeat (cron) monitors, TLS certificate alerts, page speed alerts and DNS record changes do not reach Pushbullet. See the coverage table.