Weekly Netlify build health report for every site in your team

PromptCreate

Every Monday at 9am, build me a weekly deploy health report covering every site in my Netlify team, and email it to our engineering lead. This is a retrospective rollup across the whole team account, not an alert about a single broken deploy.

Start with Netlify List Team Sites to enumerate every site in the team. Do not report on just the site that failed most recently. For each site returned, call Netlify List Site Deploys and Netlify List Site Builds and gather the activity from the last seven days. Deploys come back newest first, so you can stop paging through a site's history once you reach records older than the window.

From those records, work out per site: the number of deploys in the window, how many succeeded versus failed, the resulting success and failure rate, and the average build duration. Derive all of this from the state field and the timestamps on the deploy and build records. Important: do not attempt to report build minutes consumed or bandwidth usage. Those come from Netlify's paid analytics feature, which is not available here and will simply fail for accounts without that plan. Deploy state and timestamps are enough for counts, rates, and durations.

Then reason about the numbers rather than dumping them. I want you to identify which sites got flakier this week compared with their earlier record in the window, which failures repeated across multiple deploys and therefore look like a persistent problem rather than a one off, and which sites have not deployed at all. Where several failures on a site share a pattern, say so explicitly instead of listing each failure separately.

Write the result as a readable report, not a table dump. Open with the two or three things actually worth acting on this week, stated plainly, before any per site detail. Then give the per site breakdown with the counts, rates, and average build duration. Finish with a separate section listing sites that had zero deploys in the window, called out as possibly stale or abandoned so someone can decide whether they are dormant on purpose. Send this using Gmail Send a Message to the engineering lead, with a subject line that includes the week ending date.

After sending the email, append one summary row per site to a Google Sheets spreadsheet using Append Values, so we accumulate a running history of build health over time. Each row should carry the week ending date, the site name, the deploy count, the success count, the failure count, the success rate, and the average build duration, in a consistent column order every week so the history stays comparable.

What does this prompt do?

Checks every site in your Netlify team once a week, not just the one that broke most recently.
Works out how many times each site deployed, how often those deploys succeeded or failed, and how long builds typically took.
Opens with the two or three things actually worth acting on, then gives the per site detail underneath, and calls out sites that did not deploy at all as possibly stale.
Adds one summary row per site to a spreadsheet each week so you accumulate a running history of build health over time.

What do I need to use this?

A Netlify account connected to General Input, with access to the team whose sites you want covered.
A Gmail account to send the report from, plus the email address of the engineering lead who should receive it.
A Google Sheets spreadsheet with a sheet set aside to collect the weekly history rows.

How can I customize it?

Change the day and time it runs, for example Friday afternoon instead of Monday morning.
Send it to a whole engineering alias or several recipients instead of one lead.
Widen or narrow the reporting window, for example a rolling two weeks instead of seven days.
Adjust what counts as flaky, so only sites past a failure rate you care about get flagged.

FAQs

Do I need a paid Netlify plan for this?

No. The report is built from your ordinary deploy and build history, which is available on any plan. It does not rely on the paid analytics add on.

Does the report include build minutes or bandwidth usage?

No. Those figures come from a separate paid analytics feature, so this report deliberately leaves them out. It covers deploy counts, success and failure rates, and how long builds took, all worked out from your deploy and build records.

Will it cover all of my sites or just the busy ones?

All of them. It starts by listing every site in your Netlify team, so quiet sites are included and the ones with no activity at all get called out separately as possibly stale or abandoned.

What if a site did not deploy at all last week?

That is treated as a finding rather than an empty row. Sites with zero deploys in the window are grouped into their own section so you can decide whether they are stable, dormant, or genuinely abandoned.

Can I send the report somewhere other than email?

The report is written to be emailed to a named recipient, and it is easy to point it at a shared engineering address instead. Every run also appends a row per site to your spreadsheet, so there is a permanent record even if nobody reads the email that week.

Related templates

Trace phishing emails to the sending IP and report abuse

Every 15 minutes, forwarded phishing reports get traced back to the server that really sent them, with a verdict in Slack and the worst senders reported.

Agentic Task

Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Agentic Task

Turn procurement portal tenders into CRM deals each morning

Every weekday at 7am, sign in to the tender portals you track, filter new notices against your bid criteria, and open a deal for the ones worth chasing.