Every 5 minutes

Post new Airtable records to Slack

Your team sees each new record in Slack within minutes of it being added.

Runs: Every 5 minutes
Apps: Airtable
AI: Not needed
Access: data.records:read

Send this to your assistant

Create a ClickRuntime automation: every 5 minutes, check my Airtable Leads table and post each new record to #sales in Slack with the name, company and email.

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

Teams that rely on Airtable as an intake point, such as a table for support requests, event registrations, equipment bookings or sales inquiries, often depend on someone remembering to look at it. A row arrives at 9:40 and sits until the afternoon, or until the person who owns the table remembers to check. The requester assumes it was received and waits, while the team does not realize anything is pending.

Every five minutes, the automation lists records created since the last check, posts the key fields of each one to a Slack channel, and stores the time of the check so the next run begins where this one ended. New rows reach the team within minutes of arriving, whichever form, person or tool created them.

It is useful for small teams and for any table where a new row means someone has to do something.

What you get out of it

Requests get a response the same morning
A Slack message within five minutes of a new row means someone can reply or start work before the requester wonders what happened. That is fast enough to feel like a live service, even for a shared inbox that nobody watches.
The team shares the same awareness
Everyone in the channel sees the record, so the person who is free picks it up, and nobody assumes someone else already noticed it. Responsibility is shared, so the work is not left to the one person who might be away.
No gaps if a form or tool changes
The alert works from the records themselves, not from one form, so rows added by an integration, an import or a teammate trigger the same message as a form submission.
Missed work becomes rare
A table that is only checked when someone remembers produces slow replies and forgotten requests. A message in Slack replaces memory with a reliable signal. A request that arrives at the end of the day is no longer left until someone remembers.
Key details are visible without opening Airtable
The post includes the fields you choose, so a manager can judge urgency on the spot. Only the records that need attention require a visit to the base. Most of the time the message is all you need.

How it works

What happens, step by step

Every five minutes, ClickRuntime checks your Airtable table for records added since the last check.
It remembers when it last looked, so each record is announced only once.
Each new record is posted to your Slack channel with its key fields, like name, company and email.

Before it runs live

Connect Airtable

What you get

RunsEvery 5 minutes

Post new Airtable records to Slacktoday, 9:00Succeeded

Slack · #salesNew lead: Jordan Ellis (Northwind), jordan@northwind.example

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

Act only on the items that match your own rules, and skip the rest
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.

new_record_alert.pyexample

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

BASE_ID = "appXXXXXXXXXXXXXX"

@on_trigger
def run(event):
    since = state.get("since") or "2000-01-01T00:00:00.000Z"
    records = http.get(f"https://api.airtable.com/v0/{BASE_ID}/Leads",
                       headers={"Authorization": f"Bearer {credentials.connection('airtable', 'work')}"},
                       params={"filterByFormula": f"IS_AFTER(CREATED_TIME(), '{since}')"}).json()["records"]
    report_fetched(len(records))
    if not records:
        return {"posted": 0}
    for r in records:
        f = r["fields"]
        notify.slack(f"New lead: {f.get('Name')} ({f.get('Company', 'no company')}), {f.get('Email')}", channel="#sales")
    state.set("since", max(r["createdTime"] for r in records))
    return {"posted": len(records)}

FAQ

Common questions

Why five minutes instead of instant?

Airtable can send webhooks, but a five-minute check is simple and reliable for most intake tables. The delay is short enough for requests, and it avoids missing records during short outages. A five-minute rhythm is a good balance between speed and reliability for intake work.

Will a record be posted twice?

No. The time of the last check is stored, and each run only looks at records created after it, so a row is announced once even if the run is delayed. Nothing is announced twice or skipped.

Which fields appear in the Slack message?

The ones you choose, such as name, email, request type and priority. Long text fields can be shortened so the post stays readable in a busy channel. Fewer fields make a cleaner message. Fewer fields make a cleaner message in a busy channel.

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 checks. Checks that find nothing new 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 15 minutesAI