Learn how to set up, configure, and maximize the value of Primary Automation Triggers to improve your daily workflow.
Primary Automation Triggers are the foundation of your workflow automation in Arrive. They are the specific events that kick off an automation rule. Understanding each trigger allows you to precisely control when and how your automations run, from the moment a loan is created until it's complete. This article provides a comprehensive guide to all available primary triggers.
Understanding the Primary Triggers
Below is a detailed breakdown of each primary trigger available in Arrive's automation rules.
New loan is created
Fires when a new loan is initiated. This can happen when a borrower starts an application using a POS link, a user manually creates a file inside the LOS, or a loan is imported via a MISMO file.
Important: This trigger fires at the very beginning of the process, before a borrower has finished their application. Automations tied to this trigger will run on incomplete applications that borrowers are actively filling out.
Loan status changes
Triggers when a loan's status is updated. You can configure it to fire when a loan's status moves forwards or backwards and lands on a specific status (e.g., triggers when status changes to "Loan Setup").
Loan date changes
Monitors specific date fields in the loan file. The automation can run when a date is:
- Set: The first time a date is entered.
- Cleared: When the date is deleted or removed.
- Changed: Any time the date is set, cleared, or modified.
Key dates include status dates, order dates (Title, HOI), the TRID date, and the "Intend to Proceed" date.
Subject property changes
Watches for changes to fields related to the subject property. Similar to date changes, it can trigger when a field is set, changed, or cleared. You can also trigger an automation if a field is changed to a specific value (e.g., run an automation only when the Subject Property State is changed to "Alaska").
Loan team changes
Triggers when a member of the loan team is assigned or changed. For example, you can create a rule to run when the Loan Processor is assigned for the first time, or if the assigned processor is changed to a specific person.
Loan info changes
Monitors select, key fields within the loan itself. A useful example is triggering an automation when the Lender is first set in the loan file.
Loan tracker status changes
Specifically watches the third-party order section (Loan Tracker). For instance, you can trigger a rule when the status for the Title order changes to "Ordered".
Loan action initiated
Ties into specific actions taken within the file, often related to third-party orders. This is particularly useful for triggering automations when:
- Credit is ordered
- AUS is run
- Disclosures are generated
- Title or HOI is ordered via the order buttons
Custom field changes
Monitors any custom fields you have created in your account. The trigger can be configured to run when the custom field's value changes to a specific value (e.g., when a "Test Loan" field is changed to "True").
Borrower info changes
Watches select fields on the borrower's profile. For example, you can trigger an automation whenever the borrower's email address is changed.
Task status changes
Allows you to run an automation when a specific task from a task template is acted upon. For example, the automation can run when a task like "Assign Lock Desk" is marked as complete.
Practice exercise
Test your knowledge in a safe environment
To truly master this feature, we recommend trying it out yourself! Follow this quick exercise to build muscle memory.
- Log into your sandbox or test environment.
- Create a new automation rule using the Loan Status Changes trigger.
- Set the rule to trigger when the status changes to Loan Setup and add a simple action, like creating a task.
- Create a dummy loan and change its status to "Loan Setup" to verify the automation runs correctly.
Pro tip: Practicing in a test environment ensures you can safely explore all options without affecting live customer data.
Troubleshooting and best practices
Best practices
- "New Loan Created" Trigger: Use this for initial file setup tasks, not for workflows requiring a fully completed application.
- "Loan Actions Initiated" Trigger: Implement validation rules with this trigger to double-check file completeness before generating disclosures or ordering services.
- Specificity: Use specific trigger conditions (e.g., "Loan Processor changes to Anna" or "Property State is Alaska") to create highly targeted workflows instead of general ones.
Troubleshooting
If you encounter an error message when saving an automation rule:
- Refresh your browser page.
- Verify all required fields for the trigger and any associated actions are filled out correctly.
FAQs
What's the difference between "Loan Status Changes" and "Task Status Changes"?
"Loan Status Changes" watches the primary loan status milestone (e.g., "Loan Setup" "Clear to Close").
"Task Status Changes" watches the status of individual checklist items that are part of a task template applied to the loan (e.g., "Initial Disclosures Sent" task is marked "Complete").
Does the "New Loan is Created" trigger fire when a borrower submits their application?
No, the new file is created long before they finish the application. The trigger will fire on applications that are still being filled out, so it should not be used for automations that require a complete application.
Can I trigger an automation based on a custom data field I created?
Yes, the "Custom Field Changes" trigger allows you to watch any custom field you have created and trigger automations based on its value.