ingestlayer/recipes

Monitor CI/CD build status in Email

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

  • toemail.outEmail
    toalerts@acme.com

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 Email

Send a transactional email to one or more recipients, addressable from event fields.

  1. 01

    set the recipient

    Enter a fixed address, or reference an event field like $event.payload.email to route per event.

  2. 02

    write subject and body

    Both accept $event.* templates. The body renders as plain text with an optional summary table of the payload.

  3. 03

    confirm the sender

    Mail goes out from mail@notify.ingestlayer.com with SPF and DKIM aligned. Set a reply-to if you want responses to reach you.

in emaildelivered
From:    mail@notify.ingestlayer.com
To:      alerts@acme.com
Subject: Payment failed — acme-inc (€240.00)

A charge failed for acme-inc.
  amount   €240.00
  reason   insufficient_funds
  attempt  2

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 Email