REST API
Push a package in and pull structured findings, exceptions, and memo fields out. You own the mapping into your objects.
Dynamics overlay
Kaaj overlays Microsoft Dynamics: extracted fields and source-linked findings write into the Dynamics records you already run. Dynamics stays the CRM spine. If Leasepath is the equipment-finance LOS on that spine, Leasepath still owns quoting, documents, and funding. You choose API, webhook, button, or email. Do not wait on a Salesforce migration to start.
What moves
What stays
Handoff
Same menu as Salesforce: API, webhook, button, or email. Rotate client secrets on your schedule; an expired Dynamics secret mid-implementation is an IT item, not a reason to rip out the overlay. Sandbox first. API docs.
Push a package in and pull structured findings, exceptions, and memo fields out. You own the mapping into your objects.
Kaaj posts JSON when analysis finishes. Your team maps the payload. Useful when Salesforce times out on a long synchronous call.
Credit or ops fires analysis on the files they choose, so credits do not run on every inbound email or portal upload.
Ingest from a shared inbox, OneDrive, SharePoint, Google Drive, or Dropbox, then write the result back to the system of record.
Implementation
Confirm whether Dynamics is CRM-only or also the origination workplace.
If Leasepath is in the stack, map Kaaj β Dynamics record β Leasepath deal, not a parallel borrower file.
Issue a sandbox app registration and rotate secrets before production.
UAT with packages that already live in Dynamics so duplicate-account rules are visible.
FAQ
Continue