Daily digest

A scheduled workflow that counts the rows added to one table in the last 24 hours, lists up to ten of them and, when the table has an enum such as status, breaks the count down by value. It goes to everyone with the role you choose, as an in-app notification and an email, at the time and time zone you set.

Daily digest: its trigger and steps

What it adds to your app

A daily schedule over one table. An in-app notification and an email to a role.

How its workflows run

Each one is a server workflow in your project: it runs on its trigger, with retries, and its runs show in the builder's log.

  1. Daily ‹entity› digest

    On a schedule: schedule daily ‹time› over ‹entity›. Then: Notify ‹role›, then Send email.

Set it up

It merges into the contract of an app you already have. Nothing is overwritten: a name you already use is refused until you pass a prefix.

  1. Pick the project

    Use the button above, or ask your coding agent with the Appbricx MCP server connected (quickstart).

  2. Point it at your tables and roles

    Leave out the ones with defaults; a wrong one is refused with the options your app has.

    ParamWhat it isExample
    entityThe table whose new rows the digest counts and lists.order
    roleThe role that receives the digest (every user with it). Optional.staff
    timeWhen it goes out, 24-hour HH:MM. Optional.08:00
    tzThe IANA time zone the time and the 24-hour window are read in (empty means UTC). Optional.Europe/London
  3. Preview, then apply to dev

    A dry run shows the diff and the check report; applying it changes your dev environment only.

  4. Deploy

    When dev looks right, deploy. Production gets a snapshot first, so you can roll back.

Use it with your coding agent

The agent reads the template, runs a dry run, shows you the diff and applies it.

Prompt
Add the Daily digest template (slug "daily-digest") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (entity: table to summarise; role: who gets it; time: time of day; tz: time zone).
MCP call
{
  "tool": "use_template",
  "arguments": {
    "slug": "daily-digest",
    "project_id": "<your project id>",
    "params": {
      "entity": "order",
      "role": "staff",
      "time": "08:00",
      "tz": "Europe/London"
    },
    "dry_run": true
  }
}
CLI
appbricx templates use daily-digest --param entity=order --param role=staff --param time=08:00 --param tz=Europe/London --dry-run

Your agent adds it. Appbricx runs it.