Developer tools

GitHub

Text yourself when a deploy fails or a release ships, from a GitHub Action or a webhook.

What you can do

  • Add a step to a GitHub Actions workflow that texts you when a deploy fails.
  • Have a workflow post to a Text Hook so you get a text when a release is published.
  • Keep your API key or hook address in a repository secret so it never sits in the workflow file.

How it connects

  • Recommended

    API

    Your own code calls DogBot’s REST API and listens to its signed webhooks.

    API in the docs
  • Text Hook

    A Text Hook is a DogBot address the app posts its own webhook to. You map its fields to a recipient and a template, and each post becomes a text.

    Text Hook in the docs

Recipes

Two recipes to start from.

Set one up as written, or change it to fit how you work. The docs have the same recipes step by step.
01With the API

Text me when a deploy fails

Starts when

A GitHub Actions deploy job fails

  1. Save a DogBot API key as a repository secret.
  2. Add a last step to the deploy job and give it if: failure() so it runs only when the job fails.
  3. Have the step call POST /v1/messages with curl and send your own number as to and a short message as text.

The text it sends

Deploy of {{repository}} failed on {{branch}}. Run: {{run_url}}

From your own number

02With a Text Hook

Text me when a release is published

Starts when

A GitHub Actions workflow that runs when a release is published

  1. Make a Text Hook in DogBot with your own number as the recipient, and save its address as a repository secret.
  2. In the workflow, post the repository name and the release tag to the hook as JSON with curl.
  3. Run it once, then map repo and tag into the template from the payload DogBot kept.

The text it sends

{{repo}} {{tag}} is out.

From your own number

Try DogBot free for 7 days.

You need a card to start the trial. After 7 days it’s $29 per month plus any tax, and you can cancel from your billing page at any time.