Recommendation Digest

Ship this workflow

Pick how you want to build it.

Try it in the dashboard Fastest Go to Workflows → New Workflow → Use sample workflow in your workspace, and select this workflow. Try it
Build with the SuprSend Agent Try the agent
Build with SuprSend MCP Set up MCP

When to use this workflow

    Personalized recommendations get generated but never reach the user. The work your product does to find them goes to waste.

    Sending each recommendation the moment it appears overwhelms users. A stream of one-off alerts feels like spam and gets muted.

    Generic recommendation emails get ignored. Picks that do not feel chosen for the user are skipped without a glance.

    Users drift away without a regular reason to come back. A weekly set of fresh picks gives a low-pressure pull to return.

How it works

1

Recommendations collect through the week

As recommendations are generated (RECOMMENDATION_GENERATED), they collect for the user through the week.

TriggerDigest
2

Duplicates removed, top picks ranked first

Repeated items are removed, the rest are ranked by relevance, and the top five are kept.

Data Transform
3

Sent as one digest on Friday

On Friday evening, the top picks go out in a single email and inbox message.

Multi-Channel
4

Skipped when there are too few picks

If fewer than three recommendations have collected, nothing is sent that week.

Digest

Best practices

    Send the digest when your audience actually browses

    Friday evening is the default. Set the Digest schedule to the day and hour your audience tends to browse, so the picks arrive when they have time to look.

    Show the top picks, not everything you have

    The digest keeps the five strongest picks and links to the rest, so a focused set lands instead of a long grid. A short, ranked list gets browsed; an everything-dump gets skipped.

    Give each pick the reason it was chosen

    "Because you watched X" earns a click; a bare grid of products does not. Carry the reason into each pick so the digest reads as chosen for the user, not random.

Common mistakes to avoid

    Putting a time-sensitive pick in a weekly digest

    A recommendation that expires in a day does not belong in a Friday roundup. Send anything time-bound on its own and keep the digest for picks that stay relevant.

    Making the recommendation digest impossible to turn off

    Recommendations are promotional, so users should always be able to opt out in their preferences. Marking the category as one users cannot unsubscribe from, or forcing a mandatory channel, takes away a choice a promotional message should always give.

    Funneling every kind of recommendation into one digest

    Product picks, articles, and people-to-follow batched into one email read as a jumble. Run a separate digest per recommendation type so each one has a clear purpose.

What users receive

The actual notifications this workflow sends, on each channel.

Recommendations Digest

Email
Recommendations Digest — Email

What good looks like

Primary signal Clicks

More users act on recommendations

More picks get opened and clicked when they arrive as one well-timed weekly digest, compared with scattered one-off alerts.

Fatigue signal Mutes

Users turn the digest off

When users mute the digest or stop opening it, the picks are too many or not relevant enough to be worth a weekly send.

Support

Frequently Asked Questions

Quick answers about setting up and running this workflow.

Friday at 6 PM in each user's own timezone, with the week's recommendations gathered into one message. Change the day and time on the Digest schedule.

Nothing is sent. The Digest holds until at least three picks have collected, so a thin message never goes out under your brand.

Repeated items are removed and the rest are ranked by relevance with the Data Transform step, so the strongest pick sits first and the user does not have to scroll for it.

Email and in-app inbox, sent with Multi-Channel, so the user can browse the picks in their mail or inside your app.

Fire a few RECOMMENDATION_GENERATED events for one user, then run the digest send from the Test button in the editor, the SuprSend Agent, or the API, CLI, or MCP. You do not have to wait for Friday.

Ship Recommendation Digest in under 5 minutes.

Build with the SuprSend Agent

Copy the prompt, paste it into the Agent in your SuprSend dashboard, and the workflow gets built for you.

Try the agent

Build it with SuprSend MCP

Set up SuprSend MCP in Claude Code, Cursor or Windsurf, copy the prompt, and the workflow builds itself in your workspace.

Set up MCP