Automations

Advanced  Reviewing every check-in by hand doesn’t scale. An automation reads a new progress entry and drafts the analysis for you — you stay the editor and approver; the AI just does the first pass.

Automations live in Vault → Automations. Today there’s one kind: the Progress Report. The whole loop looks like this:

Set one up

From Vault → Automations → Create automation, choose the Progress Report kind, then configure:

1 · Trigger. It fires when a client submits a new progress entry. Leave it to run on any entry, or set “Trigger only on form” to scope it to one check-in form (e.g. your Weekly progress check-in). Note: an ordinary intake/survey submission doesn’t trigger it — only a progress entry does.

2 · Data fed to the AI. The heart of the analysis is this check-in plus the last few (0–5; the previous check-ins are what give the AI a trend to reason about). You can also choose to include onboarding answers, a client profile snapshot, and recent chat messages.

3 · Sections the AI fills in. A report always has the same three parts (you can reword how each is written, but not add or remove them): a client-facing summary, internal notes, and a priority flag. (What each part is for — and how the client eventually sees the summary — is covered in Progress reports.)

4 · After drafting (post-actions). Up to five internal follow-ups — Notify trainer in app, Send email, Send WhatsApp, or Update a field on the entry (e.g. set its status). The pipeline never messages the client directly; those go out only after you approve.

5 · Save & activate. New automations save as a Draft. Hit Activate to make it live (you can Pause or Archive later). It only runs while active.

What it produces

Each run saves a draft report on the check-in — the client-facing summary, internal notes and priority shown above. From there it’s yours to edit, approve, discard or regenerate, exactly as if you’d written it by hand. The full anatomy of a report, the approval step, and what the client sees in their app all live in Progress reports.

You can also generate a draft on demand without waiting for a check-in: open any entry’s report panel and Generate with AI runs this same automation against that entry.

Run it & watch the runs

Once active, the automation runs itself on every matching check-in. You can also Run now… against a specific entry to test it. Each execution shows up in the automation’s run history:

Open a run to see exactly what data was sent to the AI and the raw result — handy when tuning a prompt.

Examples

• Weekly reports for everyone. Pair a Weekly Progress Tracker form (set as your check-in form) with a Progress Report automation whose trigger is “Trigger only on form → Weekly progress check-in.” Every weekly submission now drafts a report.
• Catch the urgent ones. Keep the priority section on and add a Notify trainer in app post-action — you get pinged for review, and the Urgent badge surfaces the ones that need you first.
• Auto-file the routine ones. Add an Update field on progress entry post-action to set a status (e.g. Processing) so new reports land in the right column of your Progress inbox.

Automated reports vs. asking the AI

This automation runs on every check-in, the same way each time — a dependable first draft. For open-ended questions your dashboard never anticipated (“who’s drifting?”, “compare this quarter to last”), use the conversational AI agent instead. The automation is the routine; the agent is the ad-hoc.

That’s the engine that drafts your reports. For the report itself — editing, approval, and the client experience — see Progress reports. Back to the Forms & reports overview.