October 02, 2026
Most task setups fail for a dull reason: the collecting happens in one place and the deciding happens in another. Someone drops a task in a chat, you paste it into a note, and by Tuesday the note is a wall of half-finished lines you avoid opening. A daily dashboard fixes that, but only when the data underneath it is consistent enough to filter.
What follows is the version that holds up. An Airtable base stores the tasks, an Airtable form becomes the single front door for new ones, and a Make scenario runs each morning and hands you one short list of what actually needs attention today.
The three parts of the system
Before building anything, understand the division of labour. Each piece has one job, and mixing them up is how these projects stall.
- The database (Airtable): the source of truth. Every task lives here exactly once, with a status, a due date and an owner.
- The form (Airtable Forms): a four-field intake page you can bookmark. It writes straight into the base, so nothing gets retyped.
- The automation (Make): the scheduled worker. It queries the base each morning, filters out the noise and sends the results to your inbox or Slack.
That last part matters more than it sounds. The dashboard isn't a screen you remember to open; it's a message that arrives whether you're in the mood or not.
Step 1: Build the Airtable base properly
Create a base called something unglamorous like Tasks and a single table inside it. Resist adding a second table for projects on day one — linked records are useful later, but they add friction while you're still learning the shape of your own work.
The fields you need
Keep the field list tight. Every extra field is another thing to fill in and another thing that can be blank.
- Task — single line text, the only required field.
- Status — single select with exactly four options: Not started, In progress, Blocked, Done.
- Priority — single select: Today, This week, Someday.
- Due — date field. Leave it empty for anything without a real deadline.
- Area — single select for the two or three buckets of your life or job: Client work, Admin, Personal.
- Owner — single select if tasks are shared, otherwise skip it.
- Notes — long text, for the context you'll forget by Thursday.
- Created — created time, added automatically for every record.
Now add two views. A grid view called All tasks, sorted by Due date, and a second grid called Today with a filter: Status is not Done, and Due is on or before today. Airtable's TODAY() function inside a filter condition does this without any automation at all. That view is your manual fallback if Make ever breaks.
Step 2: Turn the form into your front door
Open the form builder from the Airtable toolbar and point it at the Tasks table. Hide everything except Task, Due, Priority and Area. Four fields is short enough that you'll actually use the bookmark instead of dumping the thought into a note.
Two small settings do most of the work here. Turn off the field for Status entirely, so every task arrives as Not started — otherwise you'll create records that skip the queue. And add a description to the Due field that says plainly: leave blank if this isn't real. Vague deadlines are the main reason daily dashboards drown.
Copy the public form link to your bookmarks bar and your phone's home screen. If you work with other people, share the same link rather than asking them to message you; one intake route beats twelve.
Step 3: Wire up the Make scenario
In Make, create a new scenario and add Airtable's Search Records module as the first step. Connect your account, pick the base and the Tasks table, and set a filter formula:
{Status} != "Done" AND OR({Due} <= TODAY(), {Priority} = "Today")
Set the maximum number of returned records to something above the default, usually 50 or 100, so a busy week doesn't get silently truncated. Then schedule the scenario to run once a day, around the time you start work.
Turn the records into something readable
Search Records returns a bundle per task, which is useless as an email. Add a Text aggregator module, set the source to the Airtable module, and build a line: task name, a dash, the area, and the due date if there is one. Use a newline as the separator.
From there, send it anywhere. Gmail's Send an email module works, and so does a Slack message to a private channel. If you want both, drop a Router in after the aggregator and branch to each.
Two details worth getting right on the first pass. Set the scenario's timezone to your own, because Airtable dates arrive in ISO format and a mismatch will quietly shift your "today". And add an error handler set to Ignore on the aggregator, so a day with zero matching tasks ends the run cleanly instead of emailing you a failure notice.
Step 4: Give yourself a dashboard view too
The morning email covers the push. The pull side is an Airtable Interface — one page, no configuration rabbit hole. Add a record list filtered to Status is not Done, group it by Priority, and put a second list below it showing everything that's blocked. Interfaces look decent on a phone, which matters if you check tasks between meetings rather than at a desk.
Don't try to build a kanban board, a calendar and a chart on the first day. A grouped list and a blocked list cover roughly everything a daily review needs.
Common snags and how to fix them
- Duplicate records. Usually caused by using Watch Records instead of a scheduled Search Records. For a digest, query on a schedule; watch triggers are for reacting to changes.
- Blank rows in the digest. Empty date fields render as an empty string. Wrap the field in an ifempty() in the aggregator text, or split the line into two versions.
- Tasks that never leave. If nothing gets marked Done, the list grows forever. Add a Friday habit: open the base, close out anything finished, and delete what you're honestly never doing.
- Formula fields coming back as text. Rollups and formulas return strings, so date comparisons in Make need parsing before you filter on them.
- Operation limits. Every record returned counts against your plan. Filtering inside Airtable, not inside Make, keeps runs small.
Keeping it alive past week two
The system will only survive if maintenance is boring. Once a week, spend ten minutes in the base: mark things Done, move the genuinely urgent items to Priority Today, and check the Make scenario's run history for red errors. If a field hasn't been filled in for a month, delete it — unused fields make the form slower to complete and the filters harder to trust.
Add new fields sparingly and never rename one that a scenario depends on without updating the filter formula in the same sitting. That single habit prevents most of the silent breakage these builds suffer from.
Start with the form and the base this afternoon. Run the Make scenario manually once, check the email reads the way you'd want to read it at 8am, then let it run. A dashboard you didn't have to open is a dashboard you'll still be using in three months.
Photo: Василь Вовк / Pexels
