Kipu + Salesforce integrationKipu and Salesforce, finally talking to each other
Admissions works in Salesforce. Clinical works in Kipu. We connect them both ways, so a patient is created in Kipu with one click, and admits, discharges and program history flow back to Salesforce without anyone re-typing them.
- One-click "Send to Kipu" from the Salesforce record
- Admit and discharge dates, discharge types and program history back in Salesforce
- Multiple Kipu locations, transfers and re-admits handled
900+ integrations completed · Salesforce partner · We sign BAAs
- • New patient (facesheet)
- • Emergency contacts and guardians
- • Insurance
- • Level of care and admitting location
- • Admit and discharge dates
- • Discharge type and discharged to
- • Program history
- • Referral source and referred-to
The gap between admissions and clinical
Without an integration, someone copies the patient into Kipu by hand, typos creep into insurance details, and Salesforce never finds out who admitted, who left, or where they were discharged to. Reports on lead-to-admit, length of stay and alumni outreach end up built on guesses.
What it does
What the Kipu + Salesforce integration handles
"Send to Kipu" button
Creates the patient in Kipu from the Salesforce lead or opportunity, with demographics, contacts, insurance and level of care, and opens the record in Kipu.
Checks before it sends
Missing or invalid fields are highlighted on the record before anything is pushed, so incomplete facesheets never reach Kipu.
Documents go with the patient
Insurance card images, the pre-admission assessment and verification of benefits documents are attached in Kipu.
Admits and discharges flow back
Admit date, discharge date, discharge type and where the patient was discharged to update Salesforce, and stages move automatically.
Program history in Salesforce
Every level of care and program a patient moves through, kept as history on the Salesforce record for reporting and alumni work.
Referral sources stay matched
Referral source and referred-to data sync, so referral partners get credit for the admissions they send.
Try it: connect two systems
Click and drag the blue plug back, then let go to connect Kipu to Salesforce.
AimingThe real thing
See it in Salesforce
The Send to Kipu panel on the Salesforce record, in its three states. Screenshots from a live client build, with names replaced.
- 1Ready
Everything Kipu needs is filled in, so the button is live.
- 2Blocked
Missing fields are named before anything is sent, so incomplete patients never reach Kipu.
- 3Sent and accepted
Kipu patient ID, status, a guard against sending twice, documents attached, and a link straight into Kipu.
The real thing
Catch the patients that slipped through
Some patients get admitted in Kipu without ever being sent from Salesforce. A reconciliation screen inside Salesforce lists them, suggests likely matches, and lets the team link or create the record in one click. Screenshots from a live client build; every name, date of birth and record number is made up.
- 1Every unlinked Kipu patient, in one list
Facility, admit date, program and MR number from Kipu, with a suggested Salesforce match and how confident it is. Filter by facility, then accept the match or fix it.
- 2No match? Create it
One click creates the patient account and the opportunity in Salesforce, already linked to Kipu.
- 3Patient exists, new stay
For a returning patient, search the existing account and add a new opportunity for this admission.
- 4Already in Salesforce
Search the opportunities and link the Kipu patient to the right one, so it stops showing up as unlinked.
Data that flows
Kipu + Salesforce integration: both directions, field by field
- New patient (facesheet)Name, date of birth, contact details, address
- Emergency contacts and guardians
- InsuranceCarrier, member and policy numbers, subscriber, payer IDs
- Level of care and admitting location
- DocumentsInsurance cards, assessment, VOB
- Admit and discharge dates
- Discharge type and discharged toCompleted, transferred, left against medical advice
- Program historyEvery level of care and stay
- Referral source and referred-to
- Record IDsMR number and patient IDs kept on both sides
See your own Salesforce + Kipu map
A free call maps your fields and data flow, so you see exactly what the integration would do before anything is built.
Built for real life
Kipu + Salesforce integration: the hard parts, already solved
More than one Kipu
Groups with several facilities or several Kipu accounts are routed to the right location and instance.
Transfers
Moves between programs, between facilities, and between Kipu accounts are tracked as one patient journey.
Re-admits
Returning patients are matched to their existing record instead of creating duplicates, in both systems.
Historical patients
Past admissions and discharge dates are loaded into Salesforce, so reporting starts with full history.
Mismatch alerts
A daily summary flags records that exist in one system but not the other, with an error log for anything that fails.
Patient data kept secure
Built for HIPAA: we sign a BAA, credentials are stored encrypted, and each system only gets the access it needs.
What clients say
The JTS team are extremely knowledgeable when it comes to advertising attribution and maximizing the potential of customer and leads. They know software extremely well, and how all the pieces fit together perfectly. I highly recommend his services to anyone looking to streamline their technology and maximize their sales potential.
I have been thoroughly impressed with the results. JTS team expertise in systems and software integration has given me clear and concise reports, they help me also with generating qualified leads, has been instrumental in driving my business forward. Thank you for everything you have done for my business.
For the past five years, Journeys Through Search has been an incredible marketing company to assist in our PPC, web development and support. Quick responses, vast knowledge and marketing creativity made them such a value add to our organization.
How it works
How the Kipu + Salesforce integration goes live
- 1
Free call
We look at how admissions and clinical work today and map the data between Salesforce and Kipu.
- 2
Field mapping
A mapping document and diagram for every field, signed off by your team before we build.
- 3
Build in a sandbox
The integration is built and tested in a Salesforce sandbox against your Kipu account.
- 4
Test, train and go live
QA with real scenarios, training for admissions, then go live with monitoring and support.
Working with us
US and overnight hours
Our teams cover all hours, so work keeps moving after your day ends.
AI agents in the workflow
We use AI agents in development and content creation, on a HIPAA-compliant Claude Enterprise license, so builds move faster.
900+ integrations completed
We have done this before, and it shows in how we plan and test.
Free call first
Honest advice before any work starts, even if you never hire us.
Who the Kipu + Salesforce integration is for
- Addiction treatment and mental health centers using Salesforce and Kipu
- Groups with several facilities or several Kipu accounts
- Admissions teams tired of re-typing patients into Kipu
- Leaders who need lead-to-admit and length-of-stay reporting they can trust
Kipu + Salesforce integration FAQ
Do we need Kipu API access?
Yes. Kipu currently charges $250 a month for API access, paid directly to Kipu, and the application takes 7 to 10 days. We help you apply and set up the connection.
Can it handle more than one facility?
Yes. Several locations and several Kipu accounts are routed to the right place, including transfers between them.
What happens to patients already in Kipu?
We can load historical patients, admit and discharge dates into Salesforce, so reports include them.
Is it HIPAA compliant?
We build it to HIPAA standards and sign a BAA. Access is limited to what each system needs, and credentials are stored encrypted.
How long does it take?
It depends on the project: your fields, locations and documents. You get a timeline with the quote after a free call.
How is it priced?
By project, not by the hour. The first call is free. If you want something specific first, we start with a 3-hour starter that ends in a clear deliverable. Then you get a project quote for the full integration.