Zendesk QA (formerly Klaus)

Business software

Built when you ask for it

Sync Zendesk QA (formerly Klaus) review, rating, conversation, and user 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 Zendesk QA connector syncs your support conversation-review data into analytics-ready tables in your data warehouse. Pull reviews, ratings, conversations, and users from the Zendesk QA API (formerly Klaus), 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:

  • Reviews
  • Ratings
  • Conversations
  • Users

How it gets built

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

What you will need

API key (Bearer token). Account admins generate the token, plus an account ID and workspace ID, via an API connection inside Zendesk QA's account settings.

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 Zendesk QA (formerly Klaus) connector?
Not as a finished connector yet. Ingest builds it from Zendesk QA (formerly Klaus)'s own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Zendesk QA (formerly Klaus) 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.

Zendesk QA (formerly Klaus) API documentation: https://pub.klausapp.com/

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 Zendesk QA (formerly Klaus)