Digest by Zapier, a Zapier email digest or a batched notification
Digest collects data from one or more Zaps and releases it in a single batch, like a Friday email of every lead that came in that week. Digest steps use no tasks.
Without Digest, a Zap sends a message every single time it runs. Digest saves each item into a named batch instead, then releases the whole lot at once.
You choose when it releases: daily, weekly, monthly, when it reaches a set number of entries, or manually from another Zap. If a count based digest doesn't fill up within a month of its first entry, it releases anyway with whatever it has.
Several Zaps can feed the same digest, and when it releases it empties and starts again. Digest steps don't count towards your task usage. A digest needs a trigger, the Digest step and an action to send it, so check zapier.com/pricing to see which plans include it before you build one.
I use Digest when a team is drowning in notifications. Twenty Slack pings a day about new enquiries get ignored. One tidy summary at 9am gets read.
It's also useful for managers who want to know what's happening without being in every channel. A weekly roundup of completed jobs or new leads, sent on Friday afternoon, does the job without anyone building a report.
The Digest step uses no tasks. The email step is an action, so it uses tasks like any other.
No. Digest steps don't count towards your task usage. Any action steps in the Zap, like the one that sends the digest, use tasks as normal.
Yes. Give every Digest step the same title and they'll all feed one batch.
Set the frequency to Manual, then use a separate Zap with the Release Existing Digest action to send it.
I set these up and train your team, in your own ClickUp or Zapier account.
Book a callContact Jack - jack@withtoki.co.uk