Automation Rules
Have LendingWise create tasks, send e-mails, fire webhooks, change a file's status or assign staff when something happens on a loan file.
Automation rules are the if-this-then-that layer of LendingWise. A rule watches for something happening on a loan file, such as a status change, a completed workflow step or a submitted web form. When your conditions match, the platform acts for you.
Where: Automated Actions in the back office (manager access). It has four tabs: Tasks, Email, Webhooks and Rules.
How a rule is built
Every rule has the same shape: someone does something → your conditions match → your actions run.
- Build the actions first. On the Tasks, Email and Webhooks tabs, define what can happen: a task (name, assignee, due date), an e-mail (sender, recipients, template, attachments) or a webhook (endpoint and data to send).
- Then create the rule on the Rules tab. Choose its conditions and attach one or more actions.
Two actions don't need building in advance: change the primary file status and assign a back-office employee are picked on the rule itself.
Conditions
Conditions combine with And / Or.
| Condition | The rule fires when… |
|---|---|
| Primary File Status | The file reaches a status you choose |
| File Sub Status | A particular sub-status is set |
| Workflow Steps | A workflow step is reached or completed |
| Create / Update Loan File | A file is created or saved (use deliberately) |
| Branch, Broker, Loan Officer | The file belongs to, or moves to, that party |
| Borrower Status / Borrower Type | The borrower matches |
| Loan Program | The file is on that program |
| Draw Management Status | A scope of work, draw request or revision is submitted |
Timing
- Instant: queued as soon as the change is saved. Allow a short delay.
- Scheduled: runs at a set time. Build date-based reminders here.
- No of Days: checked once a day. "Has this file been in this status for exactly X days?" is how you build stall alerts. These never repeat.
A rule fires once per file unless you tick Allow rule to repeat. Some triggers, such as completing a workflow step, can show users the matching actions first so they can untick one; this depends on a user permission.
Before you switch anything on
Mass updates fire automation for every fileChanging the status of 400 files from the pipeline triggers every matching rule 400 times. If one of those rules e-mails borrowers, 400 borrowers get it. Check the rules on the destination status before any bulk change.
Start safe
- Settle your statuses, workflows and templates first. Renaming or deleting one can quietly break the rules that point at it.
- Make your first rule create a task for yourself, not an e-mail to a borrower.
- Add a Loan Program or Branch condition so the rule doesn't reach every file in the company.
- Test on one file, then check the Automation Activity Log.
The Automation Activity Log records every action that ran, was cancelled or was skipped, along with the reason. Search it by file ID, borrower, property address or loan number.
Servicing e-mails such as payment reminders and late notices are configured separately; see Servicing 3.0 Setup.
Full detail: in LendingWise, open Loan Origination → User Guide → The Automation Rules Engine.
Updated 5 days ago