All integrations

CircleCI webhook

CircleCI users who want status without touching config.yml.

LiveWebhooksigned URL
circleci (running) Live Activity preview
what shows on your phone

CircleCI's webhook system is the no-code alternative to the inline orb (the @circleci integration above). Configure once in project settings, no `config.yml` edits required. Fires on workflow + job lifecycle events - Chirp turns workflow events into a @build activity and job events into the activity's timeline entries.

Pick this over the orb when you don't have access to edit `config.yml` (e.g. you want to monitor someone else's pipeline without changing their code), or when you want a zero-config setup. Pick the orb if you want fine-grained start/update/end control or custom data fields.

Prerequisites

  • A CircleCI project with admin access.
  • A Chirp inspector / webhook URL.

Setup

  1. 1

    Open the project's webhook settings

    CircleCI dashboard → your project → Project Settings → Webhooks → Add Webhook.

  2. 2

    Configure

    Receiver URL is your Chirp inspector. Tick workflow-completed and job-completed for the standard activity flow. The inspector key in the URL authenticates inbound posts - leave the optional signing secret blank.

    shell
    Webhook name: Chirp
Receiver URL: https://api.chirpapp.dev/v1/webhooks/circleci?key=YOUR_KEY
Events: workflow-completed, job-completed
Certificate verification: enabled
Secret token: (optional)
  3. 3

    Save and trigger a build

    Push a commit. CircleCI fires workflow-completed on the workflow that runs; Chirp opens the @build card. As jobs in the workflow complete, job-completed events tick the activity's timeline.

What you’ll see

Card header: CircleCI logo + "CircleCI · BUILDING" + project name + branch. Activity timeline ticks each `job-completed` event. Closes green/red on the final `workflow-completed` based on the workflow's status field. Tap to open the workflow page in CircleCI.

Troubleshooting

Webhook saves but no events fire.
CircleCI shows webhook history under Project Settings → Webhooks → click the webhook → "History" tab. If history is empty, you didn't tick the right events. If it shows 4xx/5xx, the URL or secret is wrong.
I see workflow-completed but no job-completed events.
Re-edit the webhook and confirm BOTH event types are ticked. CircleCI only sends events you explicitly tick.
I'm using the inline orb AND this webhook - getting double activities.
Pick one. The orb gives you fine-grained control inside config.yml; the webhook is config-free. Running both creates two separate activity streams.
Browse all integrations