ingestlayer/recipes

Monitor CI/CD build status in Webhook

Route the build results that matter — a failed pipeline on your main branch — to where the team will actually see it, without the green-build noise.

01source

sourcesdk.eventTypeScript SDK
matchci.build.finished

02pipeline · 1 steps

  • 01CTLfilter.matchstatus = failed on main only

03destinations · 1

  • towebhook.outWebhook
    urlhttps://api.acme.com/hooks

the event

You emit ci.build.finished with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

  • repostring
  • branchstring
  • statusstringpassed | failed
  • commitstringsha
  • duration_msnumber

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit ci.build.finished
import { ingest } from "@ingestlayer/sdk";

await ingest("ci.build.finished", {
  repo:        process.env.GITHUB_REPOSITORY,
  branch:      process.env.GITHUB_REF_NAME,
  status:      job.status,
  commit:      process.env.GITHUB_SHA,
  duration_ms: job.duration,
});

route it to Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

  1. 01

    set the URL

    Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.

  2. 02

    choose auth

    None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.

  3. 03

    confirm receipt

    Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered
POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

questions

Can I mute passing builds?
Filter to failures on protected branches, so a red main build pings the team and routine green runs don't.
Do I need a CI plugin?
No — emit the event from a final pipeline step with the SDK or a curl call. Any CI that can run a script can report.
Can I track build time over weeks?
Send every build to Postgres with duration_ms; the trend is then a query, independent of which builds alerted.
build this pipelineor read the quickstart →

CI/CD build status, routed elsewhere

more, into Webhook