What are workflows?
A workflow is a series of actions that a profile goes through automatically once it meets the conditions you set. Use workflows to send emails, tag profiles, move them through their lifecycle, create offers and payment plans, and alert your team, without anyone doing it by hand.
For example, when a profile moves to the Applicant, incomplete state, a workflow can wait three days, email them a reminder, and send an in-app message to their recruiter.
What's new in the Workflow builder
Rebuilt Workflow builder. Automation now lives in the Workflow builder, rebuilt with a faster, more responsive interface. Your existing workflows keep running exactly as configured.
Send in-app message. Notify staff inside Full Fabric, with a link straight to the profile or application, instead of relying on email alone.
Duplicate workflow. Copy an existing workflow and change only what differs.
More lifecycle conditions. Lifecycle workflows can now target profiles using tags and segment-builder conditions such as Has an application.
Readable workflow lists. The workflow list now describes conditions and actions in plain words, for example the target state of a transition or the template an email uses.
Where you can build workflows
You can build workflows in nine areas of Full Fabric. Each area starts and stops workflows on the events that matter there.
Area | A workflow starts when… |
Lifecycle workflow groups | A profile moves to a lifecycle state for a group of classes or courses |
Forms | A form is submitted |
Events | Someone registers for, or attends, an event |
Offer templates | An offer is made, accepted or declined |
Evaluation templates | An evaluation is assigned or submitted |
Classes | A profile moves to a lifecycle state in one specific class |
Application templates | An application is started or submitted |
Segments | A profile enters a segment |
Payment plan templates | A payment plan or fee changes, for example is paid |
Areas marked Previous still use the earlier builder layout. They are being moved to the new builder, and work the same way in the meantime.
Only staff with the right permissions can create or edit workflows. If you can't see the Automation tab, ask your Full Fabric admin.
For more detail on specific areas, see Segment workflows and Evaluation automation workflows.
How a workflow is built
Every workflow has four parts, read top to bottom in the builder.
Trigger (When). The event that starts the workflow, such as a form being submitted or a profile moving to a lifecycle state.
Conditions (optional). Extra rules a profile must meet to enter. All conditions must be true (they are joined with AND).
Actions. What the workflow does, in order. Add Wait steps between actions to space them out.
Exit condition. When a profile leaves the workflow early. Once it is met, the remaining actions don't run for that profile.
Conditions you can use
The conditions on offer depend on the area:
Profile field – available in every area. Target profiles by any profile field value, for example nationality or year of entry.
Forms and Events – a specific answer to a field in the form or event, for example everyone who ticked 2027 for their start year. See Trigger workflows by specific answers to Forms and Events.
Applications – the primary-choice programme and campus.
Classes – whether the class is below, or at or above, its maximum capacity.
Lifecycle workflow groups – tags and segment-builder conditions such as Has an application, so you can run different workflows for the same journey.
Offers – no additional conditions.
Create a workflow, step by step
Open the area you want to automate (for example a form, an event, or a lifecycle workflow group) and go to its Automation tab.
Click Add workflow and give the workflow a clear name, such as Incomplete application – 3-day reminder.
In When, choose the trigger that starts the workflow.
Add any conditions a profile must also meet. Skip this step to include everyone who matches the triggers
Click Add step and choose an action. Fill in its settings (see the action reference below).
Repeat for each action. Put a Wait step before any action that shouldn't run straight away.
Choose an exit condition, or keep the default All actions have been completed.
Save the workflow and set it live. Only profiles that meet the trigger from now on enter it; it doesn't run for past events.
Tip: to build a workflow that is similar to one you already have, open the existing one and choose Options → Duplicate workflow, then change only what differs.
Workflow actions
Actions are the steps a workflow carries out. You can combine as many as you need in one workflow, or split them across workflows when different people need different things.
Actions at a glance
Action | What it does | What you set up |
Send email to profile | Emails the profile in the workflow | Email template, subject, sender, whether it is a marketing email, optional CC/BCC |
Send email to staff | Emails chosen staff members about the profile | Email template, subject, staff recipients |
Send email to proxy | Emails the person who started or submitted the application on the applicant's behalf | Email template, subject, sender, marketing setting |
Send in-app message | Notifies staff inside Full Fabric, linking to the profile or application | Recipients, fallback recipient, title, message |
Send SMS message to profile | Texts the profile | Message, the phone field to use |
Send letter to profile | Generates a letter from a template and emails it to the profile | Letter template, email template, attachments, CC/BCC |
Create a transcript | Creates a transcript document for the profile | Nothing extra |
Send transcript to profile | Generates a transcript and emails it to the profile | Transcript template, email template, subject |
Send form submission notification to staff | Tells a staff address that a form was submitted | Staff email address |
Send event registration notification to staff | Tells staff that someone registered for the event | Staff recipient |
Add tag to profile | Adds one or more tags to the profile | Tags |
Transition profile | Moves the profile to another lifecycle state | Target state and substate |
Add profile to class | Adds the profile to the classes you pick | Classes, state and substate |
Add profile to classes by names or ids | Adds the profile to the class or programme they chose in a form field | The form field holding their choice |
Create and make offer | Creates an offer for the profile from a template | Offer template |
Create payment plan | Creates a payment plan for the profile from a template | Payment plan template, whether to publish it |
Wait | Pauses the workflow before the next action | A number of days, or days before a key date |
Which actions are available where
Action | Lifecycle | Classes | Applications | Forms | Events | Offers |
Send email to profile | Yes | Yes | Yes | Yes | Yes | Yes |
Send email to staff | Yes | Yes | Yes | – | – | Yes |
Send email to proxy | – | – | Yes | – | – | – |
Send in-app message | Yes | Coming soon | Coming soon | Yes | Yes | Yes |
Send SMS message to profile | Yes | Yes | Yes | Yes | Yes | Yes |
Send letter to profile | Yes | Yes | Yes | – | – | Yes |
Create a transcript | Yes | Yes | – | – | – | Yes |
Send transcript to profile | Yes | – | – | – | – | Yes |
Send form submission notification to staff | – | – | – | Yes | – | – |
Send event registration notification to staff | – | – | – | – | Yes | – |
Add tag to profile | Yes | Yes | Yes | Yes | Yes | Yes |
Transition profile | Yes | Yes | – | – | – | Yes |
Add profile to class | – | – | – | Yes | Yes | – |
Add profile to classes by names or ids | – | – | – | Yes | Yes | – |
Create and make offer | Yes | Yes | – | – | – | – |
Create payment plan | Yes | Yes | – | – | – | – |
Wait | Yes | Yes | Yes | Yes | Yes | Yes |
Send in-app message is also available in evaluation template workflows. Segment and payment plan workflows have their own action sets; see Segment workflows and How to associate a payment plan to students or applicants.
Send email to profile
Sends an email from one of your email templates to the profile in the workflow. In some areas it is called Send email; it is the same action.
Under Is this a marketing email?, choose Yes to send only to subscribed profiles, or No (the default) to send to everyone. Marketing emails include an unsubscribe link and the recipient's latest marketing policy agreement.
In Offers and Classes you can also choose to create a draft instead of sending, so staff can review it first.
Send email to staff
Sends a real email, built from a template with your own subject line, to the staff members you choose. Use it when staff need the detail in their inbox. For a quick alert inside the platform, use Send in-app message instead.
Send in-app message (new)
Sends a notification to staff inside Full Fabric. Clicking it opens the profile, or the application when the workflow has one. Use it to tell recruiters and admissions staff when a candidate needs attention.
Recipients. Choose specific staff members, the profile's journey owner, or all staff with a given role. Journey owner only appears where the workflow can work it out.
Fallback recipient (optional). Used only when the main choice finds nobody, for example when a profile has no journey owner. With no fallback, the action is skipped and the reason is recorded on the workflow run.
Title and message. Both accept merge tags. The merge tags offered depend on the area you are in.
Good to know:
Staff must have access to the profiles the workflow targets. You can't save the workflow if a chosen recipient lacks access.
Staff who have switched off workflow messages in their notification preferences won't receive it.
Each recipient gets one message per run. A step that runs again for the same profile on the same day doesn't send a duplicate.
Send email to proxy
Applications only. Emails the person who started or submitted the application for the applicant, such as an agent or parent. Settings are the same as Send email to profile.
Send SMS message to profile
Texts the profile. Write the message and choose which phone field on the profile to send it to.
Send letter to profile
Generates a letter from your letter templates and emails it to the profile. Merge fields for the course, offer and payment plan fill in the same way as when staff send the letter from a profile.
Create a transcript and Send transcript to profile
Create a transcript adds a transcript document to the profile. Send transcript to profile generates one from a transcript template and emails it, using the email template and subject you choose.
Send form submission notification and Send event registration notification
A short, fixed alert telling staff that a form was submitted or someone registered for an event. You can't edit its content. For a custom message, use Send email to staff or Send in-app message.
Add tag to profile
Adds the tags you choose to the profile. Tags are useful for later filtering, for segments, and as conditions in lifecycle workflows.
Transition profile
Moves the profile to the lifecycle state and substate you choose, for example from Applicant, submitted to Applicant, under review. This can start other lifecycle workflows that listen for that state.
Add profile to class and Add profile to classes by names or ids
Both add the profile to a class, in different ways:
Add profile to class adds everyone to the classes you pick from a list, in the state you set.
Add profile to classes by names or ids reads the profile's own choice from a form field. If the field holds programme names or ids, the profile joins the programme's next upcoming class. If it holds class names or ids, they join that exact class.
Create and make offer
Creates an offer for the profile from the offer template you choose, so offers go out the moment a profile reaches the right state.
Create payment plan
Creates a payment plan for the profile from a payment plan template. Choose whether to publish it straight away so the profile can see it.
Wait
Pauses the workflow before the next action. Put a Wait before every email in a sequence so messages are spread out. There are two kinds:
Fixed time. Wait a set number of days, for example wait 3 days, then send a follow-up.
Until a dynamic date. Run the next action a set number of days before the Application close date, Class start date or Class application close date. For example, remind applicants 4 days before the deadline.
Exit conditions
An exit condition takes a profile out of a workflow as soon as a goal is reached, even if actions are still waiting to run. Keep the default All actions have been completed if you want every profile to go through every step.
For example, a form workflow tags a lead, emails them, waits 3 days, emails again, waits 4 days and sends a final email. With the exit condition Profile starts any application, a lead who starts an application during the first wait gets no further emails.
Exit condition | Forms | Events | Classes | Applications |
All actions have been completed | Yes | Yes | Yes | Yes |
Profile starts any application | Yes | Yes | Yes | – |
Profile submits any application | Yes | Yes | Yes | Yes |
Profile is withdrawn, moves to another state, or the journey is deleted | – | – | Yes | – |
Application or class applications closed | – | – | – | Yes |
Profile has withdrawn | – | – | – | Yes |
Managing your workflows
Edit a live workflow
Changes to a live workflow apply only to profiles that enter it afterwards. Profiles already part-way through keep following the version they started with.
Duplicate a workflow
Open the workflow and choose Options → Duplicate workflow. The copy keeps the trigger, conditions and actions, so you only change what differs. Available in lifecycle workflow groups, classes, forms, events, offer templates and application templates.
Suspend a workflow
Use Options → Suspend to pause a workflow you'll need again later. Suspending stops new profiles from entering. Profiles already in it continue until they finish or meet the exit condition.
Delete a workflow
You can delete a workflow from its settings panel. Before you do, check whether profiles are still part-way through it.
Check what ran
The workflow list shows each workflow's conditions and actions in plain words, so you can see what it does at a glance. Admins can see scheduled workflows and their run history in the Workflows dashboard; see Webhooks and Workflow management.
FAQs
Do my existing workflows need changing after the move to the new builder?
No. Existing workflows keep running exactly as configured. Only the look of the builder has changed.
Will a new workflow run for profiles that already met the trigger?
No. A workflow only picks up profiles that meet its trigger after it goes live.
Can I use OR between conditions?
Additional conditions are always joined with AND. For forms and events, you can match several answers to the same field; see Trigger workflows by specific answers to Forms and Events.
Why didn't a staff member receive an in-app message?
Check that they have access to the profile, that workflow messages are switched on in their notification preferences, and that the recipient option found someone. If nobody was found and no fallback was set, the action is skipped and the run records why.
Can a workflow create a task or assign an owner?
Not yet. These actions are on our roadmap.
Where can I find more answers? See FAQs about Automations & Workflows, or contact your Customer Success Manager.
