Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Enable Outreach Kaia data on existing Outreach Connector

Answered
Michael Theron User
We plan to ingest Outreach Kaia call‑transcript data into our data platform using Fivetran. As part of this, we would prefer to leverage Fivetran’s existing pre‑built Outreach connector, which is designed to streamline integration, reduce custom development effort, and ensure ongoing compatibility with Outreach’s API. This approach should provide a more reliable and maintainable ingestion path compared with building and managing a bespoke solution
 
Please can you integrate the Outreach Kaia call-transcript data into the existing Outreach connector

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Abdul Ghaffar Fivetranner
    • Edited

    Hi Michael, Abdul from the product team here. Thanks for the context. Outreach doesn't expose full Kaia transcript content through their API, only recording metadata (such as start/end times, duration, host details, participant names and emails etc). Full transcripts are only available via Outreach's Kaia Daily Export (to SFTP, S3, or Azure Blob), which means we can't support this within the existing Outreach connector. Would you still be interested in syncing that via the existing Outreach connector?

    Alternatively, if you configure Kaia's Daily Export to Fivetran's SFTP connector -(https://fivetran.com/docs/connectors/files/sftp) it supports unstructured file replication (https://fivetran.com/docs/using-fivetran/features/unstructured-file-replication) for Snowflake, Databricks, and BigQuery destinations. This would get the full Kaia transcript data into your platform via Fivetran.

     

  • Jonas Bauer User

    Poking around Outreach's current public API (https://api.outreach.io/api/v2/schema/openapi.json), it looks like there's now a kaiaRecordings resource, and the recording object seems to carry a transcriptUrl field, which their schema describes as a self-authenticating URL you can use to fetch the transcript as JSON (it expires after a couple of hours). So unless I'm misreading it, it seems like the transcript content might actually be reachable through the API now, and not only through the Kaia Daily Export.

    That said, I'd take this with a grain of salt, I haven't actually fetched one of those URLs against a live org yet to confirm what comes back is the full transcript, so it's possible there's a catch I'm not seeing.