Daily

Get warned when your table stops getting records

If a form breaks and nothing new arrives for a day, you find out the same day.

Runs: Daily
Apps: Airtable
AI: Not needed
Access: data.records:read

Send this to your assistant

Create a ClickRuntime automation: every day at 6pm, email me if no new records were added to my Airtable Leads table in the last 24 hours.

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

Some Airtable tables are expected to grow every day: sign-ups from a landing page, orders from a form, leads from an ad campaign, entries from a survey. When a form is unpublished by accident, a connection to another tool is deleted, a field is renamed and breaks the link, or a website redesign removes the embed, nothing complains. The table just stops growing. Weeks later someone asks why leads are down, and the answer is that the form has been dead since the 3rd.

Each day, the automation looks for records whose CREATED_TIME falls in the last 24 hours. If there are none, it emails you. On days when records did arrive, it stays silent.

It is a safety net for lead capture, registrations and any other data feed that normally has activity every day.

What you get out of it

Broken forms are found in a day
A silent failure costs leads every hour. A one-line email after 24 hours of nothing turns a weeks-long outage into a one-day problem. The cost of the problem is the days it goes unseen, not the fix itself.
Lost leads are limited
A form that takes ten sign-ups a day loses seventy in a week of unnoticed downtime. Catching it early recovers most of that value. Every day of downtime means missed customers who will not come back to try again.
Integrations are watched without extra tools
The check looks at the result, which is new rows, so it catches any cause: a form, an automation, a webhook or a permission change. You do not need to know why it failed to know that it did, and that is the point of checking.
Silence is safe when things are fine
The email only arrives when there is a problem, so it is taken seriously instead of being filtered away as routine noise. An alert that only appears when something is wrong keeps its value.
Marketing spend is protected
If an ad campaign sends visitors to a page whose form is broken, every click is wasted. A prompt alert lets you pause the campaign or fix the form quickly.

How it works

What happens, step by step

Every day, ClickRuntime counts how many records were added to your Airtable table in the last 24 hours.
If there is at least one, it does nothing.
If there are none, you get an email warning you, so you can check that your forms are still sending.

Before it runs live

Connect Airtable

What you get

RunsDaily

Get warned when your table stops getting recordstoday, 9:00Succeeded

Email · No new leads in 24 hoursNothing was added to the Leads table since this time yesterday. Check your forms are still sending.

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 Airtable 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.

no_new_records_alert.pyexample

from clickruntime import on_trigger, credentials, http, notify

BASE_ID = "appXXXXXXXXXXXXXX"

@on_trigger
def run(event):
    records = http.get(f"https://api.airtable.com/v0/{BASE_ID}/Leads",
                       headers={"Authorization": f"Bearer {credentials.connection('airtable', 'work')}"},
                       params={"filterByFormula": "IS_AFTER(CREATED_TIME(), DATEADD(NOW(), -1, 'days'))",
                               "maxRecords": 1}).json()["records"]
    if records:
        return {"new_leads": True}
    notify.email_me("No new leads in 24 hours",
                    "Nothing was added to the Leads table since this time yesterday. Check your forms are still sending.")
    return {"new_leads": False}

FAQ

Common questions

What if my table is quiet on weekends?

You can run the check only on weekdays, or use a longer window such as 48 hours on Mondays. That prevents false alerts for tables that normally have no weekend activity. Tables with different rhythms can each have their own window.

Can it check more than one table?

Yes. List the tables and the window for each, and the email says which ones had no new records. A single message can cover several forms. The email can name each table that was quiet, which makes checking quicker.

How is this different from a new-record alert?

A new-record alert tells you when something arrives. This one tells you when nothing arrives, which is the signal of a broken form or feed that would otherwise go unnoticed. Both can run together for a well-covered intake process.

What permissions does it need?

data.records: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 (daily). 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.

Hourly or daily