On a schedule

Get a weekly deploy summary per project

Each Monday you see how many deployments succeeded and failed in every Vercel project last week.

Runs: On a schedule
Apps: Vercel
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every Monday at 9am, email me a table of last week's Vercel deployments for each project, with the number that were ready and the number that errored.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

An engineering lead running six or seven Vercel projects has no single place that says how the week went. Each project shows its own deployment list, so the count of Ready versus Error builds only exists if someone opens every project and tallies by hand. Usually nobody does, and a marketing site that failed nine of its twelve builds goes unnoticed until a stakeholder asks why their change never appeared.

Every Monday the automation pulls the last seven days of deployments from your Vercel account, groups them by project and by state, and emails you one table: for each project, how many deployments reached Ready and how many ended in Error or were canceled. The picture is waiting in your inbox before standup starts.

It suits agencies with a project per client and platform teams that own many services, where the question is less about one failed build and more about which projects keep struggling.

What you get out of it

One table instead of seven tabs
The Monday email lists every project with its success and failure counts side by side, so you read the whole portfolio in under a minute instead of clicking through each project's deployment history one at a time.
Find the project that keeps breaking
A project with four failures out of five deploys stands out in the table. That pattern usually points to a flaky build step or a missing environment variable, and you can raise it before it turns into a Friday incident.
Numbers for the retro
When the team looks back on the sprint, the table gives a shared factual starting point. Discussion shifts from impressions of how deploys felt to actual counts per project, which keeps the retrospective short and specific.
Trend you can compare week to week
Because the same email lands every Monday, you can scroll back and see whether failed builds are falling after a CI fix or climbing after a dependency upgrade, and you can credit or question the change with evidence.
Client reporting without extra work
Agencies can paste the table into a status update to show how often a client site shipped last week, which makes the maintenance retainer easier to justify and saves someone an hour of screenshotting dashboards.

How it works

What happens, step by step

Every Monday at 9, ClickRuntime gathers all your Vercel deployments from the last seven days.
It counts how many succeeded and how many failed in each project.
The table arrives in your inbox.

Before it runs live

Connect Vercel

What you get

RunsOn a schedule

Get a weekly deploy summary per projecttoday, 9:00Succeeded

Email · Weekly deploymentsproject | ready | errored storefront | 42 | 3 docs | 11 | 0

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Vercel steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

get_a_weekly_deployment_summary.pyexample

import time
from collections import defaultdict
from clickruntime import on_trigger, credentials, http, notify

TEAM_ID = "team_your-team-id"

def deployments(**params):
    resp = http.get("https://api.vercel.com/v6/deployments", params={"teamId": TEAM_ID, "limit": 100, **params},
                    headers={"Authorization": f"Bearer {credentials.secret('VERCEL_TOKEN')}"})
    resp.raise_for_status()
    return resp.json()["deployments"]

@on_trigger
def run(event):
    since = int(time.time() * 1000) - 7 * 24 * 3600 * 1000
    stats, until = defaultdict(lambda: {"READY": 0, "ERROR": 0}), None
    while True:
        page = deployments(since=since, **({"until": until} if until else {}))
        for d in page:
            if d["state"] in ("READY", "ERROR"):
                stats[d["name"]][d["state"]] += 1
        if len(page) < 100:
            break
        until = page[-1]["created"]
    rows = ["project | ready | errored"] + [f"{p} | {s['READY']} | {s['ERROR']}" for p, s in sorted(stats.items())]
    notify.email_me("Vercel deployments last week", "\n".join(rows))
    return {"projects": len(stats)}

FAQ

Common questions

Does the summary include preview deployments or only production?

The query reads all deployments from the last seven days, so previews and production both count unless you ask for a filter. If you only care about production, tell your AI assistant and the grouping can be limited to the production target instead.

Which Vercel states are counted as failures?

Deployments that end in the ERROR state are counted as failed, and READY ones as successful. Builds that were canceled are listed in their own count so they do not inflate the failure number for a project that was merely superseded.

What happens if a project had no deployments last week?

Projects with no deployments in the seven-day window simply do not appear in that week's table. A quiet project is not an error, and it shows up again in the next summary as soon as it has deployed something.

What permissions does it need?

read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (on a schedule). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Every 5 minutes