CircleCI

Developer Tools

Continuous integration and delivery platform for building, testing and deploying code.

Signature verification supported 5 events supported

Why use Hookfire with CircleCI?

Instant push notifications

Get notified on your phone the moment a CircleCI webhook fires. No more checking dashboards.

Subscribe to what matters

Choose exactly which CircleCI events trigger notifications. Filter out the noise.

Team-wide delivery

Control who on your team gets notified and how: push notifications, record only, or both.

Setup in under 2 minutes

Copy a webhook URL, paste it in CircleCI, and you're done. No code required.

Supported events

Event	Sample notification
Workflow failed `workflow-completed.failed` ❌ webhook-service: build-test-deploy failed Pipeline #130 in circleci/webhook-service failed	❌ webhook-service: build-test-deploy failed Pipeline #130 in circleci/webhook-service failed
Workflow canceled `workflow-completed.canceled` 🚫 webhook-service: build-test-deploy canceled Pipeline #130 in circleci/webhook-service was canceled	🚫 webhook-service: build-test-deploy canceled Pipeline #130 in circleci/webhook-service was canceled
Workflow succeeded `workflow-completed.success` ✅ webhook-service: build-test-deploy passed Pipeline #130 in circleci/webhook-service succeeded	✅ webhook-service: build-test-deploy passed Pipeline #130 in circleci/webhook-service succeeded
Workflow errored `workflow-completed.error` ⚠️ webhook-service: build-test-deploy errored Pipeline #130 in circleci/webhook-service hit an error	⚠️ webhook-service: build-test-deploy errored Pipeline #130 in circleci/webhook-service hit an error
Workflow unauthorized `workflow-completed.unauthorized` 🔒 webhook-service: build-test-deploy unauthorized Pipeline #130 in circleci/webhook-service was blocked by a permission check	🔒 webhook-service: build-test-deploy unauthorized Pipeline #130 in circleci/webhook-service was blocked by a permission check

What people use CircleCI alerts for

Know when your code ships, and when it breaks Pull requests, deployments and production errors, without a pager rotation.

How to connect CircleCI

Step 1: Create an Integration

Go to your organization’s Integrations page.
Click Add Integration and select CircleCI.
You’ll receive a unique Webhook URL. Copy it.

Step 2: Add the Webhook in CircleCI

You need to be an organization admin.

In CircleCI, select your organization, then Projects.
Click the … next to the project and choose Project Settings.
Open Webhooks and click Add Webhook.
Give it a name (e.g., “Hookfire”) and paste your Hookfire webhook URL into URL.
Under events, tick Workflow Completed.
Fill in Secret token (see Step 3), then click Add Webhook.

A project can have up to 5 webhooks.

Step 3: Signing Secret

Type a long random string into CircleCI’s Secret token field.
Paste the same string into the Signing Secret field on your Hookfire integration page.
CircleCI signs every delivery with HMAC-SHA256 in the circleci-signature header, and Hookfire verifies it automatically.

Step 4: Subscribe to Events

CircleCI sends one event when a workflow finishes and puts the outcome in it. Hookfire splits that by outcome, so you can switch on Workflow failed and leave Workflow succeeded off.

Job Completed events are not turned into notifications, so there is no need to tick them in CircleCI.

Step 5: Test

Click the Test button next to an event on your integration page, or re-run a workflow. CircleCI’s Test Ping Event button sends a shortened payload with no workflow outcome, so it does not produce a notification.

Supported Events

Event	Description
`workflow-completed.failed`	A workflow finished with a failed job
`workflow-completed.error`	A workflow hit an error (for example a config problem)
`workflow-completed.success`	A workflow passed
`workflow-completed.canceled`	A workflow was canceled
`workflow-completed.unauthorized`	A workflow was blocked by a permission check

Reference: Outbound webhooks and the webhook payload reference.