Five9

Five9 is a cloud contact center platform for inbound, outbound and digital customer engagement. This connector brings your Five9 domain configuration (users, skills, campaigns, dispositions, lists, IVR scripts and more) and the detail reports of your domain (call logs, agent states, logins and others) into your warehouse, so operations teams can analyze agent performance, call outcomes and campaign activity.

Setup Instructions

Follow the setup steps guide for configuring your Five9 connection to enable data to flow into your destination via DLH.

Supported Features

Here are key features supported for this connector.

Sync Feature	Supported	Details
Custom Data and Development	✓	Ability to enhance connector upon request
Historical Re-Load/Load	✓
Incremental/Delta Load	✓	Report tables add only the days completed since the last read; configuration tables are read in full
Column Selection	✓
Column Hashing	✓
Re-Sync Table/Entity	✓	Select at the table level to reload data history (on next Sync Bridge run)
Custom Queries		Utilizing SQL Data Query Connector
Custom Data
Captures Deleted Rows
API Sync Bridge Initiation	✓
Priority Scheduling	✓
Private VPC/Link	☂
DLH Data Model Available	-

If you have any questions about these supported features please reach out to our Customer Support team.

Details on Sync Processing

Configuration tables are read in full on every run.
Reports are read for whole days in US Pacific time, which is the time zone Five9 uses for every report. The first synchronization, and any historical re-sync, rebuilds each report table from the Historical Start Date, or the last year without one, in monthly windows. Later runs add only the days completed since each table was last read, so each day is read once.
A day that fails to read is read again by the next run. A report added later reads its own history.
Each report row carries the window it was read in (DLH_WINDOW_START and DLH_WINDOW_END), which shows the period an aggregate report row covers.
Five9 allows 120 report runs an hour per domain, shared with any other integration on your domain, so a first synchronization of a year takes a few hours; daily runs take minutes.
A report table keeps its history on Snowflake, Azure Synapse, Redshift, PostgreSQL, MotherDuck and SQL Server targets; on other targets it holds the most recent run.
Report tables (call logs, agent states, logins, ring attempts, digital channel logs, list, contact, do not call, worksheet, campaign and ACD queue details, and any custom reports you add) are created in addition to the configuration tables below, so the full list is visible after you create the connection.
Five9 ends username and password access for users migrated to the Five9 Identity Service, and legacy authentication, on July 15, 2027, so keep the connection user out of that migration.
This connector is currently in beta. This connection only ever reads and never changes anything in Five9.

Issue Handling

If any issues occur with the connection simply return to the sources page in DLH.io, edit the source details and click the Save & Test button to confirm connectivity. If any issues persist please contact our support team via the DLH.io Support Portal.

Replicated Entities

The following entities are replicated by default to your Target Connection. These are the table names you will see in your Target Connection. If you believe any entities/tables are missing please open a ticket with Customer Support:

Configuration tables:

USERS
USER_SKILLS
AGENT_GROUPS
USER_PROFILES
CAMPAIGNS
CAMPAIGN_SETTINGS
CAMPAIGN_DNIS
CAMPAIGN_LISTS
CAMPAIGN_STRATEGIES
CAMPAIGN_PROFILES
CAMPAIGN_PROFILE_DISPOSITIONS
CAMPAIGN_PROFILE_FILTERS
DISPOSITIONS
SKILLS
LISTS
CALL_VARIABLE_GROUPS
CALL_VARIABLES
CONTACT_FIELDS
PROMPTS
IVR_SCRIPTS
WEB_CONNECTORS
DIALING_RULES
DNIS
SPEED_DIAL_NUMBERS
VCC_CONFIGURATION

Schema Details (ER Diagram)

This entity relationship diagram (ERD) provides you with information about what entities/tables DLH provides for you out-of-the-box and how they are related to one another.