Sunfire Integration Data Mapping
Audience: Admins, Developers, Agentic Workflow Builders, Support & Operation teams, and Solution Architects
Purpose: Explains what data is sent between Kizen and SunFire and when that data is exchanged during quoting and enrollment.
Overview
This page describes how data is exchanged between Kizen and SunFire during a SunFire session and completed enrollment. When SunFire is launched from a Contact Record, Kizen sends required demographic information to pre-fill the quote or enrollment experience.
Once the session and enrollment are complete, SunFire returns enrollment and session details back to Kizen. This data exchange helps keep Contact Records up to date, supports accurate Record matching, and ensures enrollment information is captured consistently across both systems.
When data is sent vs returned:
Data is sent from Kizen to SunFire when a user launches SunFire from a Contact Record. This data is used to pre-fill the quoting or enrollment experience.
Data is returned from SunFire to Kizen after a SunFire session or enrollment is completed. Returned data includes enrollment details and selected session information, which are used to update the Contact Record in Kizen.
Data Sent from Kizen to SunFire
Data is sent from Kizen to SunFire in two scenarios: when launching SunFire from a Contact Record, and when starting a new session (for customers with token-based authentication).
Initial Launch
When you launch SunFire from Kizen, the Contact Record must include the basic demographic fields listed below. All other fields are optional.
Basic demographics (Name, Date of Birth, Address)
Contact Record
ZIP Code (required to view plans)
Contact Record
When Creating a New Session (Token-Auth Customers)
For customers configured with a crm_partner_id and token-based authentication, Kizen sends additional session data when the agent selects Create new session in the launch modal:
Providers
Contact Record
Only the first provider address matching the Contact's ZIP code is sent, to prevent duplicate doctor entries. This may not guarantee the preferred address is sent.
Pharmacy
Contact Record
Only the most recent pharmacy from the Contact Record is sent.
Drugs
Contact Record
All drugs on the Contact Record are sent.
Note: If any providers, drugs, or pharmacies cannot be matched in SunFire's system, Kizen displays a warning message identifying the unmatched records.
Data Returned from SunFire to Kizen
Kizen receives information from both the enrollment and session once the process is complete.
Enrollment data returned to Kizen:
First Name
Last Name
Email
Home Phone
Address (street, city, state, county, ZIP)
Gender
DOB: (mm/dd/yyyy)
FIPS (county code)
Medicare ID
Fields returned to Kizen from a session include:
Providers
Pharmacy
Drugs
Note: Syncing is additive. Data added in SunFire is written to the Contact Record in Kizen, but removing data in SunFire does not remove it from Kizen. To maintain a clean Record, manually remove any unwanted session data in Kizen before launching SunFire.
What's Next
Next, continue to SunFire Contact Matching Rules to understand how returned enrollment data is matched to existing Contacts in Kizen and how duplicate Records are prevented.
Last updated
Was this helpful?