Daily

Send a daily team reminder and log it in Airtable

Your team gets the same reminder in Slack each day, and every one sent is logged in Airtable.

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

Send this to your assistant

Create a ClickRuntime automation: every weekday at 11am, post 'Time to update your timesheet' to #team in Slack and add a row with today's date to my Airtable Reminders table.

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 need people to do the same thing every day, such as post standup notes, log their hours, check inventory counts or confirm a safety walk, often rely on a reminder that gets ignored. Someone posts it in Slack, a few people react, and a few do not, but nobody has a record of who did what. At the end of the month, a manager cannot say who has been consistent and who has not, and compliance questions have no data behind the answers.

Each day, the automation posts the reminder in Slack and creates a log record in Airtable for that day. As people respond, their replies can be recorded against it. Once a week, it counts the logs and posts a summary of who responded and how often.

Teams that benefit most include small operations teams, remote teams with a daily ritual, and any process where you need proof people completed a routine.

What you get out of it

Routines become measurable
A weekly count of who responded and who did not turns a vague sense of participation into numbers that a manager or a team can talk about calmly. Honest numbers make follow-up conversations easier.
Compliance has a record
For checks that must be done daily, such as safety or cleaning logs, Airtable holds a dated entry for each day. That is useful in an audit or an insurance review.
Reminders do not depend on one person
Because the reminder posts on schedule, it does not stop when the usual poster is on leave. The routine continues through holidays and sick days. The process outlives any single person's schedule, which is the point of automating it, and managers sleep better.
Gentle accountability without nagging
The weekly summary reminds the whole team about participation in one message, so the manager does not have to message individuals about missing a day. People tend to respond more when they know a summary is coming.
Patterns are easy to see
Looking at several weeks of logs shows which days are skipped most often. You might discover that Fridays need an earlier reminder, or that one shift is rarely covered. That is the kind of insight that never emerges from a chat thread.

How it works

What happens, step by step

Every day at the time you choose, the automation posts your reminder to your Slack channel, like "Time to update your timesheet".
Each reminder sent is logged as a record in your Airtable table.
Once a week, it counts the reminders in the log and posts a short summary to Slack.

Before it runs live

Connect Airtable

What you get

RunsDaily

Send a daily team reminder and log it in Airtabletoday, 9:00Succeeded

Slack · #teamTime to update your timesheet

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.

recurring_reminder_with_tracking_in_airtable.pyexample

from datetime import date
from clickruntime import on_trigger, credentials, http, notify

BASE_ID = "appXXXXXXXXXXXXXX"

@on_trigger
def run(event):
    notify.slack("Time to update your timesheet", channel="#team")
    resp = http.post(f"https://api.airtable.com/v0/{BASE_ID}/Reminders",
                     headers={"Authorization": f"Bearer {credentials.connection('airtable', 'work')}"},
                     json={"records": [{"fields": {"Date": date.today().isoformat(),
                                                   "Reminder": "Timesheet"}}]})
    resp.raise_for_status()
    return {"logged": resp.json()["records"][0]["id"]}

FAQ

Common questions

How are responses recorded?

Replies to the Slack message, such as a reaction or a short message, can be written to the day's log record with the person's name. Tell your AI assistant which form of response should count.

What does the weekly summary contain?

The number of days logged, who responded and how many times, and which days had no responses. It is posted in the same channel so the whole team sees it. That makes it easy to follow up with those who missed it.

Can different people get different reminders?

Yes. The reminder can be sent to separate channels or people on separate schedules, each with its own log table or log view, to suit shifts or roles. Each can have its own schedule and its own time.

What permissions does it need?

data.records:read, data.records:write. 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