RetireFlo

Audience: Admins, Developers, Solution Architects

Purpose: Provides a high-level look at the features and capabilities of the RetireFlo integration for AgentCRM.

Overview

With the RetireFlo integration, you receive RetireFlo survey submissions in AgentCRM in real time, automatically create new Records or update existing Records in AgentCRM on the basis of these surveys, and utilize their data in Agentic Workflows.

Note: This integration is exclusive to AgentCRM and is set up from RetireFlo, not the Kizen App Marketplace.

For more information, see Connect AgentCRM to RetireFlo.

What Is the RetireFlo Integration?

The RetireFlo integration connects AgentCRM to RetireFlo. Once you establish the connection, survey submissions in RetireFlo automatically update Records in AgentCRM. The integration refreshes AgentCRM Contacts with demographic data on current or prospective clients and their associated pharmacies, medications, and providers.

When to Use the RetireFlo Integration

Use the RetireFlo integration when you want to automate the transfer of data from survey submissions in RetireFlo to AgentCRM. Once the data exists in AgentCRM, you can work with it in Agentic Workflows.

Note: If you transform or update survey data in AgentCRM, you can't write it back to RetireFlo at this time. To protect the integrity of the original survey data, the connection goes one way only.

Common Use Cases

Here are some common use cases of the RetireFlo integration:

Check which Medicare Advantage or Part D plans are most appropriate for a prospect based on their medications or preferred providers.
Proactively identify clients whose plans might no longer be optimal based on provider participation.
Utilize up-to-date information about the client's healthcare to improve the speed, accuracy, and effectiveness of follow-up calls.

How the RetireFlo Integration Works

Before you configure the RetireFlo integration, it's important to understand how it functions at a conceptual level.

Connection Model

The integration connects AgentCRM to RetireFlo through a preconfigured global OAuth application. Because of this, authentication is quick and secure. You don't need to generate additional API keys or set up AgentCRM to connect.

See Connect AgentCRM to RetireFlo for more information.

Survey Field Mapping

Survey data in RetireFlo maps to specific data structures in AgentCRM. When someone submits a survey on the RetireFlo side, the integration passes the relevant data to the corresponding Records and Custom Fields on the AgentCRM side. Specifically:

Client data in RetireFlo maps to Custom Fields of Contacts in AgentCRM.
Pharmacy data in RetireFlo maps to Custom Fields of Pharmacy Objects in AgentCRM.
Medication data in RetireFlo maps to Custom Fields of Medication Objects in AgentCRM.
Provider data in RetireFlo maps to Custom Fields of Provider Objects in AgentCRM.

The following expandable sections describe these mappings in more detail.

Client Data Field Mapping

Client data in RetireFlo maps to the following Custom Fields of AgentCRM Contacts:

Kizen Field

Type

Description

First Name

String

The client's first name.

Last Name

String

The client's last name.

Email

String

The client's email address.

Mobile Phone

String

The client's mobile phone number. This string must consist of digits only and be exactly 10 characters long.

Street Address

String

The client's street address.

Street Address 2

String

The second line of the client's street address, if any.

City

String

The client's city of residence.

State

Object

The full name of the client's state of residence, mapped internally to the corresponding two-letter abbreviation.

Zipcode

String

The ZIP code associated with the client's street address.

Birthday

String

The client's date of birth in YYYY-MM-DD format.

Pharmacies

Array

An array of pharmacy IDs for the pharmacies associated with the client Record.

Medications

Array

An array of the medication IDs for the medications associated with the client Record.

Providers

Array

An array of the provider IDs for the providers associated with the client Record.

Pharmacy Data Field Mapping

Pharmacy data in RetireFlo maps to the following Custom Fields of AgentCRM Pharmacy Objects:

Kizen Field

Type

Description

Name

String

The NPI or name of the pharmacy.

Pharmacy Name

String

The name of the pharmacy.

NPI

String

The NPI of the pharmacy.

Phone Number

String

The pharmacy's phone number. This string must consist of digits only.

Street Address

String

The pharmacy's street address.

Street Address 2

String

The second line of the pharmacy's street address, if any.

City

String

The city in which the pharmacy is located.

State

String

The two-letter abbreviation corresponding to the state in which the pharmacy is located.

Zip

String

The ZIP code associated with the pharmacy's street address.

Medication Data Field Mapping

Medication data in RetireFlo maps to the following Custom Fields of AgentCRM Medication Objects:

Kizen Field

Type

Description

Drug Name

String

The NDC or name of the medication in the following format: {ndc_or_drug name}-{quantity}.0-{frequency}

Name and Dosage

String

The prescription name and dosage of the medication in the following format: {prescription_name} {dosage_name}

NDC

String

The NDC of the medication

Quantity

Number

The quantity prescribed of the medication

Frequency

Number

The supply of the medication in days: 30, 60, 90, 180, or 365

Connecture Drug ID

String

The ID of the medication in ConnectureDRX

Connecture Dosage ID

String

The ID of the medication's dosage in ConnectureDRX

Note: The Connecture Drug ID and Connecture Dosage ID fields don't appear on the medication Record in AgentCRM. AgentCRM uses these values internally.

Provider Data Field Mapping

Provider data in RetireFlo maps to the following Custom Fields of AgentCRM Provider Objects:

Note: Depending on whether the submission contains data from ConnectureDRX, not every field receives a value.

Kizen Field

Type

Description

Provider Name

String

The NPI or name of the provider or hospital.

Full Name

String

The full name of the provider or hospital.

Last Name

String

The last name of the provider.

NPI

String

The NPI of the provider or hospital.

Address

String

The street address of the provider or hospital.

City

String

The city in which the provider or hospital is located.

State

Object

The full name of the state in which the provider or hospital is located, mapped internally to the corresponding two-letter abbreviation.

Zip

String

The ZIP code associated with the street address of the provider or hospital. The integration uses the first five characters only.

Note: The Last Name field doesn't appear on the provider Record in AgentCRM. AgentCRM uses this value internally.

Record Matching

When RetireFlo receives a survey submission, the integration determines whether to create a new Contact in AgentCRM or update an existing Contact based on the following logic:

The integration checks for a match in the First Name and Email fields. If a match exists, the integration updates this Contact in AgentCRM.
The integration checks for a match in the First Name and Mobile Phone fields. If a match exists, the integration updates this Contact in AgentCRM.
If neither combination yields a match, the integration creates a new Contact in AgentCRM.

Available RetireFlo Actions and Topics

For step-by-step instructions on using the RetireFlo integration, see the following topics:

What's Next

Continue to Connect AgentCRM to RetireFlo to learn how to set up the AgentCRM connection in RetireFlo.

RetireFlo is a trademark of the RetireFlo company.

PreviousTroubleshoot Postgres

NextConnect AgentCRM to RetireFlo

Last updated 11 days ago

Was this helpful?