Triggers, Filters & Actions

This page lists what a workflow can start on, how its filter narrows who goes through, and the steps it can take. How to put them together is described in Workflow Rules.

Triggers

A workflow belongs to one place, and that place decides which triggers it can use.

Workflow belongs to Trigger Starts when
Lifecycle workflow group Lifecycle state changes, with From and To A person's journey in one of the group's products moves from the From state to the To state, or is added in the To state. Any state matches every state
Form Form is submitted The form is submitted. The workflow starts for the profile each time, so one person can be in it more than once
Event Event response changes, with Starts when The chosen change happens: Response is marked as Yes, No or Maybe, Response is created, Attendance is marked as Yes or No
Application template application is started, submitted or pending payment The applicant reaches that point on an application from the template
Class profile state transitions A person's journey in the class changes state
Offer template offer is made, accepted, submitted or declined The offer reaches that point
Evaluation template evaluation is assigned or submitted The evaluation reaches that point
Payment plan template payment plan is published, is fully paid, fee is paid, first fee is paid The payment plan reaches that point
Shared segment profile enters segment A person starts matching the segment

A withdrawn journey never starts a lifecycle workflow. On events, a response workflow starts only before the event ends; an attendance workflow starts before or after it.

Segment Triggers

Segment workflows do not react to a single event: Full Fabric compares the segment's members with the previous check and starts the workflow for each person who joined. A segment, or its workflow, that was changed in the last 15 minutes is left out of the check until it settles.

Scheduled Triggers

Some system workflows run on a clock rather than on an event: Minute schedule, Hourly schedule and Daily schedule. They keep class and course states and closed application templates up to date and, where the Canvas integration is on, sync course grades. They are provided by Full Fabric and cannot be created by staff. See Running Workflows & Scheduling.

Filters

The Filter step decides who goes on. With no conditions, every profile goes on. Conditions are checked once, when the trigger fires; a person who does not match does not enter the workflow.

Source Offered on Compares
Profile All workflows A field on the person's profile
Form Form and event workflows An answer in the submission, with the operator Is one of
Capacity Lifecycle workflows Whether the class is Below the maximum capacity or Above or equal to the maximum capacity

Profile conditions use these operators, depending on the field type: Equals, Not equals, Contains, Is empty, Is not empty, In list, Not in list, Includes, Excludes, Before, After, Greater than, Less than. Date fields compare with a Specific date.

Between conditions, the connector reads and or or; select it to switch. It applies to the whole filter: either every condition must match (and) or any one is enough (or).

Workflows set up from application templates and other settings pages can also filter on the application's fields, its primary choice, and the journey owner.

Actions

Steps run one after the other, in the order shown. Select Add a step and pick one from Select action.

Flow

Step What it does
Wait Holds the person at this step for a duration, until a date, or until a number of days before a class date. See Wait steps

Messages

Step What it does
Send email Emails the person from an Email template, with Subject, Sender name, Sender email, CC and BCC. Mode is Dispatch (send) or Save as a draft. Answer Is this a Marketing email? with Yes to send only to subscribed profiles
Send SMS Texts the person at the number in the chosen Phone number field
Send letter Generates the chosen Letter templates for the person and emails them
Send transcript Emails the person their transcript from a Transcript template
Notify staff Emails the chosen Staff member about the person, with a Subject
Notify staff of the submission On form workflows, notifies the chosen Staff member of the new submission. On event workflows it reads Notify staff of the registration

Profile

Step What it does
Change lifecycle state Applies a lifecycle Transition to the person's journey
Add tag Adds Tags to the person
Create payment plan Creates a payment plan from a Payment plan template, published automatically or not
Create a transcript Creates a transcript from a Transcript template
Make offer Creates an offer from an Offer template and makes it to the person
Add to product Adds the person to Specific products, or to The products picked in the form's product fields, in a chosen State and substate
Add to product by name or ID Adds the person to the products named in a form Field

Steps by Workflow

Step Lifecycle Form Event
Wait, Send email, Send SMS, Add tag Yes Yes Yes
Notify staff of the submission or registration, Add to product, Add to product by name or ID Yes Yes
Send letter, Send transcript, Notify staff, Change lifecycle state, Create payment plan, Create a transcript, Make offer Yes

Steps that need a module are offered only when it is on: SMS needs SMS, letters and transcripts need Documents, payment plans need Billing, offers need Offers.

Workflows set up from other settings pages offer some further steps, such as Send email to proxy on application templates and Send email to assigned evaluator on evaluation templates.

Exit Conditions

Under Workflow settings, Exit in any of these conditions decides when a person leaves the workflow. Every option except All actions have been completed can end it before the remaining steps run:

Exit condition Offered on
Profile is withdrawn, transitions to another state, or the journey is deleted Lifecycle workflows
All actions have been completed All
Profile starts any application All
Profile submits any application All

Segment workflows can also exit when the profile exits the segment. An exit condition is only checked once the first step has started.