CI/CD deploys

Automatically tell your team when a build or deploy is done.

No more staring at the pipeline: with PushPig your CI/CD notifies the team automatically as soon as a build or deployment finishes — or fails. A single HTTP request at the end of the job is all it takes.

Wire it into the pipeline

GitHub Actions, GitLab CI, Jenkins or a shell deploy script — any runner that can run curl can send:

- name: Notify PushPig
  if: always()
  run: |
    curl -X POST https://pushpig.de/api/push/send \
      -H "Authorization: Bearer pp_YOUR_API_KEY" \
      -H "Content-Type: application/json" \
      -d "{\"channel\":\"deploys\",\"title\":\"Deploy ${{ job.status }}\",\"body\":\"${{ github.repository }} @ ${{ github.sha }}\"}"

Tell success from failure

Set the job to always and pass the status in the title — so you know at a glance whether the deploy went through or needs attention. For failed builds, "urgent": true makes sure the message arrives even during quiet hours.

One channel per environment

Split deploys-staging and deploys-prod into separate channels. With API key scopes a CI key can then write only to the production channel, for example — cleanly separated and locked down.

Save recurring messages as a template and let the pipeline fill in just the variables (version, environment) — consistent deploy messages without copy-and-paste.

And the other way round

Want to feed PushPig events back into your own system? With webhooks you get HMAC-signed delivery events (push.sent, push.failed) straight into your infrastructure.

Help & API · Pricing · Contact · Imprint · Privacy