Automation
Automation lets Full Fabric do routine work on its own. Staff describe it once, and the platform carries it out every time the situation comes up: email an applicant three days after they submit, notify an admissions officer when a form arrives, score each new application, remind a colleague that a call is due.
Automation has four parts:
| Part | What it does | Set up in |
|---|---|---|
| Workflow rules | When an event happens, for the people who match, run a list of steps (wait, send an email, add a tag, change a lifecycle state, make an offer) | The Automation tab of a form, event, class or template, and Settings → Automation & AI → Lifecycle workflows |
| Webhooks | Send an event to another system as it happens | Webhooks, in the settings (gear) menu |
| Agents | Score applications and people, or validate identity documents, and record the result for staff | Settings → Automation & AI → Agents |
| Tasks | To-dos staff assign to each other, with due dates and reminders | The Inbox |
Key Concepts
| Term | Definition |
|---|---|
| Workflow template | A workflow rule: trigger, filter, steps and exit conditions. Shown as a workflow on forms, events and lifecycle groups |
| Workflow (or enrolment) | One person's run through a workflow template, with its own state and schedule |
| Trigger | The event that starts a workflow or an agent run |
| Filter | The conditions a person must match, checked when the trigger fires |
| Step | One action in a workflow, such as Send email or Wait |
| Exit condition | An event that ends a person's workflow before its last step |
| Agent | A background worker that records a result for staff: a score, a verdict or a potential |
| Run | One execution of an agent on one record, kept for review |
| System workflow | A workflow provided by Full Fabric to keep the platform running |
Pages in This Section
- Workflow Rules: where workflows live, building, publishing, pausing, and the templates list.
- Triggers, Filters & Actions: every trigger, condition, step and exit condition.
- Running Workflows & Scheduling: workflow states, the runs list, wait steps and scheduled triggers.
- Webhooks: subscriptions, what is sent, retries and the activity log.
- Agents: agent types, setting them up, and AI model access.
- Reviewing Agent Runs: runs, their details, where results appear, and potential suggestions.
- Tasks: creating, assigning and completing tasks, and their reminders.
- Permissions & Limits: who can do what, and the limits that apply.
Agents at a Glance
| Agent | Trigger | What it does |
|---|---|---|
| Application scorer | Application submitted or updated | Scores the application against the institution's own criteria, written as a prompt, and records the score and justification for staff review |
| Potential scorer | Application, profile, event or form activity | Scores the person and sets the potential of their journeys |
| Document validator | Passport/ID file uploaded | Reads the document, checks it is a valid identity document, fills in the details it proves, and records a verdict shown as a badge next to the upload. See Passport/ID Field |
Scorers use the institution's AI model and need AI model access. The document validator is a system agent that reads documents without an AI model, so it works with AI switched off. The AI Console and assistant are described in AI Console & Assistant.
Note: Agent results are visible to signed-in staff wherever the underlying record is visible, for example as columns in application lists and badges on uploads.