How Do I Send One Daily Digest Instead of Dozens of Notifications?

A practical field guide from Automation Ace.

The short answer

Split alerts into two tiers. Urgent items still send right away. Everything else is collected as it happens and released on a schedule as one message, such as a 9 a.m. Slack post or a Friday email. In Zapier, use Digest by Zapier. In Make, store items and combine them with an aggregator in a scheduled scenario. In Airtable, Zapier Tables, or a sheet, flag new rows and send a scheduled summary. Each method needs to mark items as sent, so nothing is repeated or missed.

1. Decide what goes in the digest

Ask the people who get the alerts which ones need action within minutes. Those stay instant. Typical examples are failed payments, VIP or high-value leads, urgent support tickets, and automation failures. Routine items go in the digest: new sign-ups, form submissions, completed tasks, low-priority tickets, and daily stats. See Slack notification best practices.

Pick a schedule that matches how the team works, such as daily at the start of the workday, twice a day, or weekly for reports. Set the time zone explicitly. See why an automation uses the wrong time zone.

2. Build it with Digest by Zapier

Zapier has a built-in Digest tool designed for this:

1. In the Zap that currently sends each alert, replace the Slack or email step with a Digest by Zapier step that appends an entry. Map the line you want for each item, such as name, source, and a link.
2. Choose when the digest is released: on a daily, weekly, or monthly schedule, after a set number of entries, or when another Zap releases it.
3. Add the Slack or email step after the digest step, and map the combined digest text into the message.
4. Keep a separate path or filter in the same Zap that sends urgent items immediately. See why a Path runs the wrong branch.

Check how Digest and other built-in tools count toward your task usage. See Zapier apps that don't use tasks and Zapier built-in tools.

3. Build it in Make

Make has no single digest module, so build it in two parts:

1. Collect: in the scenario that handles each event, add a record to a data store or database table with the item's details and a sent flag set to false.
2. Release: a second scenario runs on a schedule. It searches for unsent items, combines them into one block of text with a text aggregator, sends the message, and then sets each item's sent flag to true.

Only mark items as sent after the message succeeds, so a failed send doesn't lose them. See Make scenario error handling.

4. Build it with Airtable, Zapier Tables, or a sheet

If the items already live in a table, you may not need a separate collection step:

• Create a view of records that are new and not yet included in a digest.
• On a schedule, find the records in that view, build one message, send it, and mark them as included.
• In Airtable, a scheduled automation can find the records and send an email or Slack message. In Zapier, a Schedule trigger plus a search for multiple records and a Code or Formatter step to join them works well. See looping and aggregating line items.

A table-based digest also gives you a history of what was sent and when. See sharing data between Zaps.

5. Format the digest so people read it

• Lead with counts: “12 new leads, 3 need follow-up.”
• Group items by type, owner, or priority, with the items that need action first.
• One line per item with a direct link to the record.
• Cap the length: show the first 20 items and link to a view or report for the rest.
• Tag owners only on the items they need to act on.

For a worked example of a scheduled summary, see the daily Google Calendar agenda in Slack.

6. Avoid common pitfalls

• Duplicates: without a sent flag, the same items can appear in two digests.
• Lost items: marking items as sent before the message succeeds loses them if the send fails.
• Empty digests: decide whether to skip sending or send “nothing new today.” A short note confirms the automation is still running.
• Hidden urgent items: review the urgent rules after a few weeks and move anything that waited too long back to instant.
• Silent failures: if the digest stops, nobody may notice for days. Add an error alert. See automation monitoring.

Frequently asked questions

What is Digest by Zapier?

Digest by Zapier is a built-in Zapier tool that collects entries from many Zap runs and releases them together as one combined message, on a schedule, after a set number of entries, or when another step releases it.

How do I build a digest in Make?

Store each item as it happens, for example in a data store or a database table, then run a scheduled scenario that finds the new items, combines them with a text aggregator, sends one message, and marks the items as sent.

Should every alert go into the digest?

No. Keep urgent, time-sensitive alerts instant, such as failed payments, VIP requests, or outages, and send everything else in the digest. Agree on the rule with the people who receive the alerts.

What should a digest do when there is nothing to report?

Either skip sending or send a short note that there was nothing new. A short note confirms the automation is still running, which is useful for digests people rely on.