AI & RAG

Email a weekly digest of all manual spec changes to field crews

On a weekly schedule, gathers every spec change logged across all manual revisions that week and emails field crews a single grouped digest with old vs new values and page links.

CategoryAI & RAG
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires Monday morning
  • ActionQuery Supabase for spec changes from the trailing 7 daysSupabaseSupabase
  • LogicExit quietly if no changes were logged
  • ActionGroup changes by equipment and summarize old vs newOpenAI
  • OutputEmail grouped digest with page links to field crewsGmailGmail

What it does

Produces one consolidated weekly email summarizing all spec changes detected across the equipment manual library, grouped by equipment, with old and new values and a link to each source page. Replaces ad-hoc 'did you see the revision' messages with a predictable briefing.

When to use it

When field crews need a regular, low-noise summary rather than a real-time ping for every change, or as a recap layer on top of live spec-change alerts. Good for distributed teams who plan jobs at the start of each week.

How it works

  1. 1A weekly schedule fires the trigger on Monday morning.
  2. 2The flow queries Supabase for all spec-change records logged in the trailing seven days.
  3. 3A logic step checks whether any changes exist and exits quietly if none.
  4. 4OpenAI groups the changes by equipment and writes a concise, skimmable summary with old vs new values.
  5. 5The digest, including per-change page links, is emailed to the field crew distribution list via Gmail.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SupabaseTables, auth, storage, edge functions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.