A. What Is the Trigger Editor?
The Trigger Editor is where admins can create or edit all parts of a trigger, including:
- Trigger name
- App (e.g., Filevine or Foundation AI)
- Event that starts the trigger
-
Trigger filters (criteria for when the trigger activates)
B. Accessing the Trigger Editor
To open the Trigger Editor:
- Go to the Trigger Menu.
- Click + New Trigger.
You’re now in the Trigger Editor dashboard.
C. Trigger Editor Dashboard Overview
The dashboard is split into two main sections:
- Trigger Details
- Trigger Name
- App
- Event
- Trigger Filters
- Criteria that define when the trigger should fire
- + Add Item to add more filters
-
Save button to apply changes
D. Creating a New Trigger
Step 1: Fill Out Trigger Details
- Enter a Trigger Name.
- Select the App:
- For Filevine: fill in Project Type, Event, and Section.
- For Foundation AI: select the Event.
- Complete all required fields.
💡Tip: The Event defines the specific moment when the trigger activates (e.g., when a new document is uploaded).
Step 2: Add Trigger Filters
Filters tell the system when to execute the process, based on data.
To add a filter:
- Make sure Trigger Details are filled out.
- Click + Add Item.
- Choose the Variable, Operator, and Value.
For Example: project.status Equals Active
- Optional: Add more filters or delete them as needed.
-
Click Save to store your trigger.
E. Need Help with Criteria?
To better understand how trigger criteria work, check out: Criteria in Neodeluxe
F. Filevine Connector
The Filevine connector allows you to trigger automations in Process Studio based on activity in Filevine projects—like form updates, new collections, or button actions.
G. Setting Up a Filevine Trigger
To create a Filevine trigger:
- Select Filevine as the App.
- Choose a Project Type (this limits triggers to projects using that template).
- Select an Event (what activity starts the trigger).
-
Select a Section (the area in the Filevine project where the event occurs).
H. Available Filevine Events
Event Name | Description |
Form Updated | Triggered when a form is edited. |
Collection Created | Triggered when a collection is added. |
Collection Updated | Triggered when a collection is edited. |
Collection Created/Updated | Fires on either create or update. |
Collection Deleted | Triggered when a collection is removed. |
Taskflow Executed | Triggered by a Taskflow Action Button. |
Taskflow Reset | Triggered when a Reset Button is used. |
Contact Created | When a new contact is added. |
Contact Updated | When a contact is edited. |
Note: Taskflow-related events are not linked to Neodeluxe Flow Tasks or Advanced Task Management—they are tied to Filevine's Taskflow Trigger Buttons.
I. How the Section Field Works
The Section dropdown will display options based on your selected Project Type and Event:
- Collection events → Show collection sections.
- Form events → Show static form sections.
- Taskflow events → Show taskflow button sections.
- Contact events → Show contact sections.
J. Example Trigger in Action
If you configure a trigger in Filevine Projects with Project Type: Immigration 2 like this:
IF
“Child Under 21” in Family Information Equals “Yes”
OR
“Does Child have United States Status” Equals “No”
THEN
When either of these fields is set with those values, the trigger activates, and any connected process starts.
Next Module: Manage Processes in Process Studio.
Comments
0 comments
Please sign in to leave a comment.