Hourly

Get alerts when too many records pile up

You hear once when a status goes over your limit, and again only after it has dropped and risen again.

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

Send this to your assistant

Create a ClickRuntime automation: every hour, post to #support in Slack if more than 20 records in my Airtable Support table have Status set to Open.

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

Work piles up in one status long before anyone says so. Tickets pile up in Waiting for customer, orders in Needs review, content in Pending approval, candidates in Screening. A single item sitting there is normal, but forty of them mean a bottleneck: the reviewer is away, an upstream step is producing too much, or a process change has made one stage slower. In an Airtable base with several hundred rows, nobody counts, so the backlog is noticed when a customer or a deadline forces the issue.

Every hour, the automation counts the records in each status and compares each count with the threshold you set. When a status goes over the line it sends an alert, and then it stays quiet until the count drops back under, so you get one alert per pile-up and not one per hour.

It is useful for team leads who manage queues, and for operations people who own a handoff between two teams.

What you get out of it

Bottlenecks are named while they are small
An alert at 25 items in Pending approval gets the reviewer's attention before it becomes 80. A short backlog clears in an hour, while a long one takes days and delays everything behind it.
One alert per pile-up, not one per hour
The state remembers that you were already warned. You are not flooded by repeat messages while the queue is being worked down, so the alert keeps its meaning and is read when it arrives.
Handoffs between teams are held to a standard
A threshold on a shared status makes the limit visible and objective. When the number crosses it, both teams know without a debate about whether the queue is really too long.
Customers wait less
If your statuses reflect customer-facing steps, such as Awaiting reply or In review, catching a backlog early shortens the time customers spend waiting for an answer. A shorter wait is something customers notice and remember.
Capacity planning is based on evidence
Seeing which statuses cross their limits, and how often, shows where you need another person or a simpler process. That is a better argument for a hire than a feeling that everyone is busy.

How it works

What happens, step by step

Every hour, the automation counts the records in your Airtable table for each status.
It compares each count with the limit you set, for example 20 open support requests.
When a status goes over its limit, it posts one alert to your Slack channel.
It stays quiet until the count drops back under the limit, so you're not alerted again every hour.

Before it runs live

Connect Airtable

What you get

RunsHourly

Get alerts when too many records pile uptoday, 9:00Succeeded

Slack · #support27 support records are Open (threshold 20)

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.

status_count_threshold_alert.pyexample

from clickruntime import on_trigger, credentials, http, state, notify

BASE_ID = "appXXXXXXXXXXXXXX"
THRESHOLD = 20

@on_trigger
def run(event):
    headers = {"Authorization": f"Bearer {credentials.connection('airtable', 'work')}"}
    count, params = 0, {"filterByFormula": "{Status} = 'Open'", "fields[]": "Status", "pageSize": 100}
    while True:
        page = http.get(f"https://api.airtable.com/v0/{BASE_ID}/Support", headers=headers, params=params).json()
        count += len(page["records"])
        if "offset" not in page:
            break
        params["offset"] = page["offset"]
    alerted = state.get("alerted") or False
    if count > THRESHOLD and not alerted:
        notify.slack(f"{count} support records are Open (threshold {THRESHOLD})", channel="#support")
    state.set("alerted", count > THRESHOLD)
    return {"open": count}

FAQ

Common questions

How does it avoid sending the same alert every hour?

It stores a flag when it has alerted for a status and clears the flag when the count falls below the threshold. A new alert is sent only if the count goes over the limit again.

Can each status have its own threshold?

Yes. A queue where 50 items is normal and one where 5 is already a problem can each have their own number. The thresholds sit in the configuration and are simple to adjust. Each threshold lives in the configuration.

Where is the alert sent?

By default to email or Slack, whichever you prefer. The message names the status, the current count, the threshold and a link to the filtered view, so the person who reads it can start work at once.

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 (hourly). 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