Skip to main content

Importing Call Recordings into Weflow Conversation Intelligence

Bring existing call recordings into Weflow with an API key from your current provider. We import them and link each one to the right Salesforce record.

Importing Call Recordings into Weflow Conversation Intelligence

Switching to Weflow Conversation Intelligence doesn't mean starting from scratch. You can bring your historical call recordings with you, so your team keeps full context on past deals, coaching moments, and customer conversations from day one.


Supported sources

Weflow supports imports from all major conversation intelligence tools, including Gong, Chorus, Jiminny, Kaia/Outreach, Fathom, Grain, Zoom and more. We can also import recordings stored in your own infrastructure, such as an S3 bucket or a data warehouse. If your provider isn't listed, reach out anyway. Chances are we've handled it before or can build the import quickly.
​

What we need from you

All we need is an API key from your current provider. Once you share it, our team handles the entire import on our end. There's no manual export, no file uploads, and no work required from your admins beyond generating the key.

If an API key isn't available, a raw file export can work as an alternative. Our team will review the export first to confirm it contains everything needed for a clean import.


Migrating recordings from S3 or a data warehouse

If your recordings live in an S3 bucket or data warehouse, we'll need access to the video or audio files along with the metadata for each recording.

The more metadata you provide, the better the result. Ideally, this includes the Salesforce record each recording should be linked to, the start and end time, the meeting title, and the participant list.
​

Granting access to BigQuery, Snowflake or Redshift

For BigQuery, Snowflake or Redshift, create a read-only role or user with SELECT access to the tables containing your recording metadata and share the credentials with our team. The recording files themselves are usually stored separately in a bucket such as S3, so please also grant read access to that bucket, for example through an IAM role we can assume. Access is read-only and can be revoked as soon as the import is complete.


Linking recordings to Salesforce

Every imported recording is automatically linked to the right Salesforce records, so your history shows up exactly where your reps expect it.

If your previous provider stores the Salesforce association and exposes it through its API, we use that data directly to map each recording to the correct account, opportunity, or contact.

If that association isn't available, we run the recordings through our own lookup service, which matches them to Salesforce records based on participants and meeting details. Recordings that can't be matched automatically can still be linked manually afterwards.


What happens after the import

Once imported, your historical recordings behave just like any recording captured by Weflow. They are transcribed, searchable, and available for coaching, scoring, and Ask AI, giving your team one place for every customer conversation, old and new.


Getting started

Contact your Weflow account manager or our support team and share the API key for your current provider. We'll confirm the scope, kick off the import, and let you know once everything is live in Salesforce.

Did this answer your question?