How to Send a Daily Airtable Status Digest to Gmail Using Make.com

Introduction

If your team still exports an Airtable view, pastes rows into an email, and sends the same status summary every morning, you are doing repeatable work that breaks when someone is out. Manual exports cause missed rows, inconsistent formatting, and late notifications.

A better approach is a daily digest that reads a saved Airtable view, compiles the meaningful fields, and sends one tidy email to stakeholders via Gmail. You will get a single email each morning with only relevant rows, simple counts, and direct links back to Airtable.

By the end you will have an actionable Make.com scenario that batches records, avoids duplicate alerts, and gives stakeholders a readable daily status digest.

What You'll Need

• An Airtable base with a saved view that contains the records you want in the digest (filter applied in the view)
• A Make.com account with Airtable and Gmail connections (Make.com paid plan recommended if you run frequent scenarios or need many operations)
• A Gmail account authorised in Make.com to send emails
• (Optional) A Google Sheets file if you want an audit log of sent digests
• Airtable API key or a service account with read access to the base

Note: Airtable enforces per-base rate limits. If your base is busy, use paged reads and batching to avoid 429 errors. See Airtable's documentation for current limits and use Make.com's webhook options where possible.

How It Works (The Logic)

Make.com runs on a daily schedule, pulls the records from a specific Airtable view, groups them into a single digest, and sends a formatted Gmail message with counts, a short summary, and a table of items. The scenario also logs which record IDs were included so the digest does not resend the same alert twice if you want one-time notifications.

Trigger (scheduled) → List records from Airtable view → Filter and batch → Build HTML email body → Send via Gmail → (Optional) Write audit log to Google Sheets

Step-by-Step Setup

1. Design the Airtable view

• Create a dedicated saved view in Airtable that filters only the records you want in the daily digest. Rely on Airtable filters instead of complex Make.com filters where possible, this reduces API calls.
• Include the columns needed in the digest, for example: record name, status, owner, updated date, priority, link formula (use RECORD_URL() or a formula field to produce a clickable link).

Gotcha: saved views return consistent columns. Changing the view later can break your mapping. Lock the view once the scenario works.

2. Create a Google Sheet for an optional audit log

• Create a small sheet with columns: digest_date, record_id, record_name, reason, digest_id.
• This sheet will prevent duplicate notifications when you only want to notify once per record.

3. Start a new Scenario in Make.com and add a Scheduler

• Add the Scheduler module and set it to run at your desired time, for example 07:00 local time on weekdays.
• For testing, run the scenario manually.

4. Add Airtable: List Records from View

• Add the Airtable module "List records" and point it to your base, table, and the saved view you prepared.
• Use pagination settings if Make.com exposes them; request the maximum page size available to reduce calls. Airtable supports up to 100 records per page. If you expect more than 100 matches, loop through pages.

Field mapping: capture record id, name, status, owner, updated time, priority, and the record URL field you prepared in Airtable.

Gotcha: respect Airtable rate limits. If you plan many such reports across bases, stagger schedules or add delays.

5. Add a filter module to short-circuit an empty digest

• Immediately after listing, add a simple condition: continue only if record count > 0.
• This prevents sending empty emails and reduces noise.

6. (Optional) De-duplication: check audit log in Google Sheets

• If you want each record to appear in a digest only once, add a Google Sheets "Search rows" module that checks whether the record ID already exists in your audit sheet.
• Use a router: one branch for new records (not logged) and one branch to skip records already logged.

Performance note: this introduces extra API calls. If your digest includes many records, perform a batch lookup by pulling the whole sheet into Make.com and using an in-scenario map/lookup to avoid one row-search per record.

7. Format and batch the records into an HTML table

• Use an Iterator module if you need to loop each record and build rows, or use the Array aggregator to assemble an array of objects then build the HTML in one step.
• A compact HTML table is best for inbox readability. Include columns such as Name (linked to the Airtable record), Status, Owner, Updated, and a short reason.

Example row template (pseudo):

Formatting tip: keep the table narrow. Many email clients collapse long tables. Test in Gmail and on mobile.

8. Add summary metrics above the table

• Before the table, compute a few summary numbers: total items, items by status (e.g., 5 blocked, 12 in progress), and highest priority count.
• Use Make.com aggregate functions or map/reduce inside the scenario to compute these counts.

9. Build the Gmail message

• Use the Gmail "Send an email" module. Set recipients to your stakeholder list.
• Subject example: "Daily status digest: {{date}} — {{total_items}} items".
• Body: include the summary counts, the HTML table, and a short instruction line like "Click an item to open it in Airtable."
• Set Content Type to HTML so the table renders.

Gotcha: Some Gmail connectors require the body to be provided as raw HTML. Ensure your HTML is well formed and tested.

10. After send: append records to the audit log

• On the branch that represented new records, add a Google Sheets "Add row" module to log each record ID with the digest date and digest ID.
• If you used a batched approach, write rows in a single bulk operation if your connector supports it. This helps stay within rate limits.

11. Test thoroughly

• Run the scenario with a small set of test records. Confirm the email arrives, links open the correct Airtable records, and the audit log updates correctly.
• Check edge cases: long text fields, missing owners, and records updated between the list step and the send step.

12. Turn on and monitor

• Activate the scenario and watch the first week of runs. In Make.com check for transient errors, 429s from Airtable, or Gmail quota problems.
• If you see rate limit issues, add a small sleep/delay or reduce frequency.

Real-World Business Scenario

A SaaS product team used this setup to send a daily digest to the executive team listing feature requests flagged as "awaiting prioritisation." The saved Airtable view filtered only requests marked by customer success. The Make.com scenario produced a short email with counts and direct links, which replaced a manual morning export and cut the time to spot urgent items from 20 minutes to under 5.

Common Variations

• PDF attachment variant: instead of an HTML email use a Google Sheets export or a Google Docs template to generate a PDF snapshot and attach it to the Gmail message. This is useful when recipients prefer a printable snapshot. See our guide on PDF generation for details: Generate a PDF from a Google Docs Template Using Make.com and Gmail.
• Slack-first digest: post the same summary and top items into Slack using a Blocks formatted message, and include a human-friendly link to the full Airtable view for the team.
• Real-time alerts plus daily digest: combine a small Make.com scenario that sends immediate alerts for critical status changes, with the daily digest for regular review.

Where to go from here

You have a repeatable pattern for an Airtable to Gmail daily digest that reduces manual exports and keeps stakeholders informed with a single, readable message each morning. If you want this implemented or extended across Airtable, Make.com, Gmail, and reporting storage like Google Sheets, Olmec Dynamics builds these automations for real businesses. Learn more about our work at https://olmecdynamics.com.