Connect · Explainer
How webhooks work.
A webhook is a message one system sends to another the moment something happens. It’s how a signed agreement in one tool becomes a new matter in another, without anyone retyping it.
The journey of one event
Four steps, in about a second.
- 01
Something happens
A client signs their fee agreement in your e-signature tool.
- 02
A signal is sent
The tool sends a short, secure message to Matterline: “agreement 4821 was signed”.
- 03
The workflow runs
Connect checks the message is genuine, then updates the CRM, files the PDF and issues the deposit link.
- 04
Everything is logged
Each step is written to a run log with the time and result, so you can see exactly what happened.
When something fails
Failures are expected, and handled.
Automatic retries
If a system is briefly unavailable, the step is retried before anyone is alerted.
Alerts to a person
If it still fails, we’re alerted and the item is queued, not lost.
Fixed within one business day
Our target for resolving failed runs, with the fix noted in the run log.
Security
Built to be checked.
Verified senders
Incoming signals are checked with signatures or secrets before anything runs.
Least data
Only the fields a workflow needs are passed between systems.
Documented
Every integration is listed in your integration inventory, with what it touches.
Start with a Practice Diagnostic.
A few short questions, then a free 30-minute conversation. You’ll leave knowing what’s worth connecting or automating first.