We are using the Fivetran Genesys connector and need two additional data sets that are not currently available. Both are needed for outbound dialer reporting going live in the coming weeks.

REQUEST 1: Outbound Contact List Contact Records (rows)

Use case: We are launching an outbound dialer and need to report on the contacts being dialled.

The existing CONTACT_LIST table covers metadata (list name, ID, column definitions, etc.) but does NOT include the actual contact records. Genesys exposes contact records via an async export process:

1. List all contact lists (already synced as CONTACT_LIST):  GET /api/v2/outbound/contactlists?pageSize=100&pageNumber=1
2. Trigger async export per contact list:  POST /api/v2/outbound/contactlists/{contactListId}/export
   Returns a DomainEntityRef. The export is queued and processed asynchronously.
3. Poll for the download URI (returns 404 until ready): GET /api/v2/outbound/contactlists/{contactListId}/export?download=false
   Returns { "uri": "<signed-url>", "exportTimestamp": "..." } once complete.
4. Download the CSV from the signed URI (requires Authorization: Bearer header).

Genesys API documentation:

• Contact list management: https://developer.genesys.cloud/routing/outbound/contactmanagement
• Export endpoint reference: https://developer.genesys.cloud/api/rest/v2/outbound/exportcontactlists

New tables requested:

• CONTACT_LIST_EXPORT — one row per export event (contactListId, exportTimestamp, uri)
• CONTACT_LIST_ROW — the actual contact records with all dynamic columns (phone number,  name, custom attributes, campaign state, etc.) — columns vary per contact list based  on its columnNames schema

REQUEST 2: Flow Datatable Schema & Rows

Use case: We use Genesys Architect data tables (flow datatables) to store configuration
data driving our IVR flows. We need to audit and report on this data.

The existing FLOW_DATA_TABLE table covers metadata (table ID, name, division) but does
NOT include the column schema or actual rows.

1. List all datatables (already synced as FLOW_DATA_TABLE):  GET /api/v2/flows/datatables
2. Fetch column schema per table: GET /api/v2/flows/datatables/{datatableId}?expand=schema
   Returns a JsonSchemaDocument with properties defining column names and types  (string, boolean, integer, number).
3. Fetch all rows per table (paginated, showbrief=false required):   GET /api/v2/flows/datatables/{datatableId}/rows?pageSize=100&pageNumber=1&showbrief=false
   Each row is a dict[string, object] matching the table's column schema. Max 10,000 rows per table.

Genesys API documentation:

• Data tables overview: https://developer.genesys.cloud/routing/architect/data-tables
• Datatables API reference: https://developer.genesys.cloud/api/rest/v2/architect/

New tables requested:

• FLOW_DATA_TABLE_SCHEMA — column definitions per datatable (datatableId, fieldNtype, isRequired, defaultValue)
• FLOW_DATA_TABLE_ROW — actual row content per datatable (datatableId, key, all  column values as typed columns or as a JSON column)

PRIORITY / BUSINESS IMPACT

Both are needed for outbound dialer reporting going live in the coming weeks.

We are aware that the contact list export pattern is asynchronous and non-trivia
implement compared to a simple paginated GET. We are happy to provide test
environments, example data, or additional technical details to support the
implementation.

Thank you!