| Runs | On a schedule |
|---|---|
| Takes | The loan system's account export |
| How | A scheduled secure upload that the site imports |
| Keeps current | The customer login portal on the lender's WordPress site |
| Replaced | A weekly manual upload |
| Tools | Microsoft Power Automate, SharePoint, WordPress |
| Our part | We contributed, working with the lender's team |
| Status | Live in production |
What does it do?
- Takes the loan system's account export.
- Sends it to the lender's WordPress site in a scheduled secure upload.
- The site imports it, so the customer login portal stays current without the weekly manual upload.
It began as a headless-browser automation of the site's admin import screen, with success and failure marker files, and was later replaced by the scheduled upload.
What doesn't it do?
- Change any figures. It carries the loan system's export to the site; the loan system stays the source.
- Use AI.
Never trust silence from the other end. If a system won't tell you whether it worked, the automation needs its own proof: a marker file, an alert, a notice email or a separate check. We plan that proof before we build.
What would this look like at your lender?
If your customer portal or website needs figures from the loan system, the first question is what the site will accept: an API, a file by SFTP or FTPS, or only an admin screen. We'd find that out on the call, then prototype the simplest route that also gives you proof it ran.
- Price: depending on what your site accepts, a standard automation at $499 or a custom build from $995, fixed in writing after the prototype.
- Watching it for you: $99 a month for monitoring, fixes and small changes, month to month.
- Ask your web host early: which file routes they allow, and whether they can confirm each import.