Docs / Data sources / Five9

Five9

Business software

Built when you ask for it

Sync Five9 call, agent, and campaign data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Five9 connector syncs your cloud contact center data into analytics-ready tables in your data warehouse. Pull calls, agents, campaigns, and dispositions from the Five9 API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Calls
  • Agents
  • Campaigns
  • Dispositions

How it gets built

  1. Choose Five9 when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Five9's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Five9 itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

OAuth2 (client credentials). An Admin Console user with API Access Control enabled generates a Consumer Key and Secret; this feature is Controlled Availability, not standard for all accounts.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Five9 connector?
Not as a finished connector yet. Ingest builds it from Five9's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Five9 data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Five9 API documentation: https://documentation.five9.com/bundle/api-docs/page/api-docs/getting-started/authentication-api.htm

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Five9