Webhooks
Tell another system that something happened on a loan file by firing a webhook from an automation rule.
A webhook is how LendingWise tells another system (your CRM, accounting system or a dashboard) that something happened on a loan file. It's the outbound counterpart to Lead Posting.
A webhook isn't a separate feature: it's one of the actions an automation rule can take, alongside tasks, e-mails, status changes and assignments.
Where to find it
Automated Actions → Webhooks tab (manager access). Build the webhook first, then attach it to a rule on the Rules tab.
Building a webhook
| Setting | What it does |
|---|---|
| Name / Description | For you; name it after what it reports. |
| URL to notify | The receiving system's address. It must be a normal public internet address; internal network addresses are refused. |
| Method | POST or GET, whichever the receiver expects. |
| Post format | Form data or JSON. |
| Format Data | Send values as proper types (numbers, dates) or as stored. |
| Status | Enabled or disabled. Disabling is a clean kill switch that leaves the rule intact. |
| Instant or Schedule | Send when the rule matches, or a number of days before, after or on a reference date. |
Then choose what to send:
- Parameters from the file: a name the receiver expects, mapped to a loan-file field
- Custom parameters: fixed values, such as an environment or event name
- Authentication parameters: whatever the receiver needs to accept the call
Every parameter name must be unique. A webhook with no parameters sends nothing.
What can trigger one
Anything that triggers a rule: status or sub-status changes, workflow steps, files created or updated, web form submissions, posted leads, the daily check and draw activity.
Mass updates fire once per fileChanging status on 400 files from the pipeline is 400 calls to your endpoint. Warn the receiving system's owner, or disable the webhook for the duration.
Renamed fields keep their original identityRelabelling a field changes your forms and pipeline, not what a webhook sends. Tell the receiving system's owner before you rename anything they depend on.
Checking delivery
Open the Automation Activity Log and filter by Webhooks. Each attempt shows the receiving system's own response, which settles most "we never got it" questions.
Test on a throwaway file with a narrow rule, have the receiver confirm the data field by field, then widen it.
Full detail: in LendingWise, open Loan Origination → User Guide → Webhooks.
Updated about 6 hours ago