REST API
Push a package in and pull structured findings, exceptions, and memo fields out. You own the mapping into your objects.
HubSpot overlay
Kaaj sits on HubSpot without becoming a second CRM. Inbound application email can still create deals and contacts in HubSpot. Kaaj analyzes the package and writes structured KYB, bank findings, and memo outputs back onto that deal. Pipeline automations stay yours. Trigger with a button if you do not want every inbound file to spend a credit.
What moves
What stays
Handoff
Email-to-deal can stay in HubSpot. Kaaj then runs on that deal via button, webhook, or API. Do not let HubSpot email and a Kaaj inbox both create the application unless you have a join key. 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
Keep HubSpot as the creator of deals and contacts if that is today’s workflow.
Map Kaaj outputs onto deal properties credit already looks at.
Choose button vs automatic so sequences do not fire analysis on incomplete mail.
UAT with a real inbound application email, not a cleaned demo file only.
FAQ
Continue