Airtable Scheduled Automations: Recurring Records, Daily Digests, and Overdue Nudges

Most Airtable automations react to something: a record is created, a field changes. A surprising amount of real operations work is driven by the calendar instead: the weekly report, the monthly compliance check, the Monday task list. Airtable's At scheduled time trigger handles these. This tutorial builds three scheduled automations on a simple task base: recurring record generation, a daily digest, and overdue nudges.

What you need

• A base with a Recurring Templates table (Task name, Owner, Frequency single select: Weekly / Monthly, Next due date, Active checkbox) and a Tasks table (Task name, Owner, Due, Status, Source template linked record).
• Permission to create automations. Check your plan's monthly automation run allowance before you start.

1. Generate recurring records

People often copy tasks by hand every Monday. Let the base do it.

1. Create an automation with the trigger At scheduled time, set to daily at 06:00.
2. Add the action Find records on Recurring Templates, using a view filtered to Active is checked and Next due is on or before today.
3. Add a Repeating group over the found records. Inside it, Create record in Tasks, mapping name, owner, and Due from Next due, and linking Source template.
4. Still inside the group, Update record on the template, moving Next due forward. Weekly adds 7 days and monthly adds one month. A small script action is the simplest way to compute this, or use a Next due after formula field and copy it across.

Make it idempotent

If the automation runs twice, or you re-run it after a failure, you do not want duplicate tasks. Because step 2 only finds templates due today or earlier and step 4 moves the date forward, a second run finds nothing. That is why the date update belongs in the same loop as the create. Never advance dates in a separate automation.

2. Send one daily digest

Fifty individual notifications train people to ignore all of them. One digest does not.

1. Trigger: At scheduled time, weekdays at 08:00.
2. Find records in Tasks using a view: Status is not Done and Due is within the next 3 days.
3. Add a script action that turns the found records into a text block. Pass the records in as an input variable, then output a string:

let records = input.config().records;
let lines = records.map(r => `- ${r.name} (${r.owner}) due ${r.due}`);
output.set('digest', lines.length ? lines.join('\n') : 'Nothing due. Enjoy the quiet.');

4. Add Send email or a Slack message, with the digest output in the body.

To send one digest per owner, put a repeating group over a view of owners and filter inside it, but keep an eye on run counts, since each action in a loop counts toward limits.

3. Nudge overdue work, once

A nudge that fires every morning for a month becomes noise. Add a Last nudged date field to Tasks. The overdue view filters on Status is not Done, Due is before today, and Last nudged is empty or more than 3 days ago. After sending, update Last nudged to today. Escalate to a manager when the task is over 7 days overdue, using a second view and a different message.

Gotchas

• Time zones. Scheduled triggers run in the time zone you pick in the trigger, and date fields without a time are compared in the base's configured time zone. Set both deliberately, or your 08:00 digest will arrive at the wrong hour after a daylight saving change.
• Test with a dry run. Use the automation's test button on a copy of the base or against a view that returns two or three records. A loop gone wrong can create hundreds of rows.
• Limits. Find-records actions return a capped number of records, and loops have step limits. If a view can exceed them, process in batches or move the logic to a script.
• Watch run history. A schedule that silently fails stays broken until someone notices a missing report. See our guide on automations that fail silently for alerting.
• Know when to pick another tool. If the logic is event-driven, a record trigger is more reliable. Our Zapier, Make, or native comparison covers the trade-offs.

Checklist before you turn it on

1. Time zone set on the trigger and checked on the base.
2. A re-run produces no duplicates.
3. Notifications are digests, not floods.
4. A failure alerts a human.
5. Run volume fits your plan.

BaseBrainers builds and audits calendar-driven workflows for operations teams as part of our Airtable for business operations work. If your schedules need a second look, get in touch.