Skip to content
Integrations/Five9/Connection Guide
Connection Guide

Connect Five9 Without Breaking the Audit Trail

Use this guide to connect Five9 or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryContact center
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Five9 and make sure the first collection lands cleanly.

  1. 1
    Create dedicated integration user (least privilege).
  2. 2
    Obtain API credentials (OAuth client or API key).
  3. 3
    Enter credentials in Aurora's secure fields, or use an external secret reference only if your policy requires it.
  4. 4
    Run validate; then enable incremental cadence.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

usernamepassword

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.