> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devhelm.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Pushbullet

> Push DevHelm incident alerts to your phone and desktop via Pushbullet

Connect DevHelm to Pushbullet to push incident notifications to your phone, browser, and desktop. DevHelm sends notes through the Pushbullet API — leave the device unset to broadcast to every device, or target a single one.

## Setup

<Steps>
  <Step title="Create a Pushbullet access token">
    1. Go to [Pushbullet Settings](https://www.pushbullet.com/#settings) → **Account**
    2. Under **Access Tokens**, click **Create Access Token**
    3. Copy the token — it's shown only once
  </Step>

  <Step title="(Optional) Find a device identifier">
    To target a single device instead of broadcasting to all, list your devices and copy the `iden` value:

    ```bash theme={null}
    curl https://api.pushbullet.com/v2/devices \
      -H "Access-Token: o.your-access-token"
    ```

    Leave `deviceIden` empty to push to every device on your account.
  </Step>

  <Step title="Create the alert channel in DevHelm">
    <CodeGroup>
      ```bash CLI theme={null}
      devhelm alert-channels create \
        --name "Pushbullet Alerts" \
        --type pushbullet \
        --config '{"channelType":"pushbullet","accessToken":"o.your-access-token"}'
      ```

      ```yaml devhelm.yml theme={null}
      alertChannels:
        - name: Pushbullet Alerts
          config:
            channelType: pushbullet
            accessToken: ${PUSHBULLET_ACCESS_TOKEN}
            deviceIden: ${PUSHBULLET_DEVICE_IDEN}
      ```
    </CodeGroup>
  </Step>

  <Step title="Test the channel">
    ```bash theme={null}
    devhelm alert-channels test <channel-id>
    ```
  </Step>
</Steps>

## Configuration

| Field         | Description                                                  | Required |
| ------------- | ------------------------------------------------------------ | -------- |
| `accessToken` | Pushbullet access token                                      | Yes      |
| `deviceIden`  | Target device identifier; broadcasts to all devices if empty | No       |

## Troubleshooting

<AccordionGroup>
  <Accordion title="Notifications not arriving (HTTP 401)">
    The access token is invalid or was revoked. Generate a new one under [Settings](https://www.pushbullet.com/#settings) → **Account** → **Access Tokens** and update the channel config. Tokens are invalidated if you reset access tokens on your account.
  </Accordion>

  <Accordion title="Pushes go to the wrong device or nowhere">
    A stale or mistyped `deviceIden` causes pushes to silently miss. Re-list devices with `curl https://api.pushbullet.com/v2/devices -H "Access-Token: ..."` and confirm the `iden`, or clear the field to broadcast to all devices.
  </Accordion>

  <Accordion title="Rate limited (HTTP 429)">
    Pushbullet enforces per-account rate limits. If you hit them during a burst of incidents, space out test calls and rely on DevHelm's incident-level (not per-check) notifications to stay within quota.
  </Accordion>
</AccordionGroup>