Thresh reads the paperwork. Your system of record keeps the result.
Every completed extraction is delivered as a signed webhook the moment it finishes, so the fields land where your team already works: the CRM, the transaction system, the back office. Two integrations are worked examples with real code and a recording against the live API; everything else is the same webhook plus an afternoon.
Follow Up Boss
A signed contract goes into Thresh and the deal shows up in Follow Up Boss: the buyers as people, a deal in the stage you name with the price and the projected close, a note on each buyer with every extracted field and the page it came from, and tasks for the closing and the inspection deadline. When the packet is grouped as a Thresh deal, the relay also lands the synthesis the moment it completes: the cross-document discrepancies, by document role, arrive as a note on the buyers the contract created, alongside their deal. One dependency-free Python relay, a few hundred lines including the retry and resume logic, written to be read and adapted.
Recorded against the production console and a Follow Up Boss trial account: upload the contract with the saved template, and the deal, the people, the note, and the task appear; then the packet is synthesized as a Thresh deal and the cross-document discrepancies land as a note on the same records. The relay answers Thresh at once and lands everything on its own schedule, so a slow CRM never costs a document. Ask for the relay.
Salesforce
A PDF attached to an Opportunity is uploaded to Thresh by an Apex Queueable; the signed webhook lands the extracted fields back on a custom object as native records, each with its page and confidence, so they feed reports, list views, and flows. A deployable SFDX reference integration, not a managed package.
Recorded against a real Salesforce Developer org and the live API. Reference code on GitHub.
Signed webhooks
Register an endpoint once and Thresh posts document.completed with the full result, and deal.completed with the synthesized summary, to it the moment they finish (plus the failed counterparts), signed with an HMAC over a timestamp and the raw body. Verifying is five lines in any language; the SDKs ship it. Deliveries retry with backoff and every attempt is in the audit log.
- Python and JavaScript SDKs.
pip install thresh-sdkandnpm install thresh-sdk: upload, wait, read, verify a webhook. See the SDK guide. - Any CRM or TMS with an API. The two examples above are the pattern: receive the webhook, map the fields, call the system's API. kvCORE, Lofty, dotloop, SkySlope, and the rest are an afternoon each, and we will build the next one with a design partner.
- No-JSON path for agents. Member seats in the console upload with a saved template and read the results; the webhooks and API keys stay with the workspace admin. See Thresh for real estate.
Access is invite-only while we work with design partners. Tell us which system your results need to land in and we will scope the integration with you.