Announcing Pingram Notifications for GitHub Actions

We shipped two GitHub Actions — Send Email and Send SMS — so you can send notifications straight from a workflow step.

Getting a notification out of CI usually means hand-rolling a curl step, keeping a JSON payload correct in YAML, and parsing the response yourself. It works until someone needs an SMS instead of an email, or the endpoint changes, or the step swallows a failure silently.

Both actions take an API key from a repository secret and a handful of inputs. The key is masked in logs, the send returns a tracking-id you can use in later steps, and fail-on-error: false downgrades a failure to a warning when a notification should never block a deploy. to accepts a comma-separated list. There are no runtime dependencies, so nothing is installed on the runner.

Pair it with if: failure() and you have build failure alerts in five lines:

- uses: pingram-io/github-actions-send-email@v1
  if: failure()
  with:
    api-key: ${{ secrets.PINGRAM_API_KEY }}
    type: ci-alerts
    to: oncall@example.com
    subject: '${{ github.workflow }} failed on ${{ github.ref_name }}'
    html: <p>Run ${{ github.run_number }} broke.</p>

See the GitHub Actions docs for setup, all inputs, and SMS examples.