# BREVIAN
> Knowledge powered Sales Intelligence Platform

Canonical page: https://collective.gong.io/integrations/brevian-c3ac7136-13f2-424c-bc20-e670ef651db3
Marketplace: Gong Collective
Last updated: 2025-12-08
Logo: https://assets.partnerfleet.app/53aeefb8o0any7bf6v98m60gjnoq

## At a glance
- Filter by Category: [Account Insights](https://collective.gong.io/t/primary-category/account-insights), [Performance Management](https://collective.gong.io/t/primary-category/performance-management), [Workflow & Automation](https://collective.gong.io/t/primary-category/workflow-and-automation)
- Business Outcome: [Ramp Time](https://collective.gong.io/t/business-outcome/ramp-time), [Rep Productivity](https://collective.gong.io/t/business-outcome/rep-productivity)
- Filter by Feature: Import Calls
- Website: [brevian.ai](https://brevian.ai)

## Call to actions
- [Connect](https://app.brevian.ai)

## About
Brevian is an AI-driven sales intelligence platform that layers on top of Gong to help teams turn conversations into actionable insights. By combining Gong call data with CRM and enablement content, Brevian delivers cross deal insights, rep coaching grounded in your sales enablement, and instant meeting summaries and custom transcript workfows —all in one place. Teams get clearer visibility, faster prep, and smarter execution without changing their existing Gong workflow.

## Screenshots
- ![Insights](https://assets.partnerfleet.app/9lnvcd6qg17nqgc1gayb7iiet76x)
- ![Chat on insights](https://assets.partnerfleet.app/nvb1kn33pvpe4o1vra9ukgumtol1)
- ![BREVIAN Chat - Loss Report](https://assets.partnerfleet.app/7wmt60qh8jru24l81k6bmt28gree)

## Features
- **Use Gong Data in Brevian** — Use Gong Transcripts for AI insights across deals, coaching and more

## Benefits
- **AI Insights** — Brevian delivers insights and trends across deals and conversationsIntuitive Chat interfacePowered by Brevian's Knowledge Graph that combines CRM + Conversations + Sales Enablement
- **Coaching and Performance** — Brevian helps reps get better with every call and saves managers time from reviewing callsPost call coaching on multiple dimensions including product knowledgeRep performance comparison to identify top rep behaviors
- **CRM Automation** — Brevian automates updates to CRMAutomatic derivation and updating of Call Summaries and Action ItemsSupport multiple frameworks like MEDDPICC, MEDDIC etc

## FAQs
### Frequently Asked Questions: Gong ↔ Brevian Integration
1. What does this integration do?This integration connects Brevian with Gong so that call and meeting data captured by Gong are surfaced in your Brevian environment. The goal is to:Automatically ingest recorded customer-facing calls and meetings from Gong into BrevianEnable Brevian to extract insights (e.g., key discussion points, objections, signals) based on those conversationsProvide your sales and enablement teams with richer context in Brevian—so they can act faster, coach better, and close deals more predictably2. Why would I want to enable it?By integrating Gong + Brevian, you get benefits like:A unified view of customer conversations plus product/market knowledge inside BrevianLess manual effort: rather than manually exporting or uploading recordings, you get seamless ingestionBetter adoption of your conversation intelligence: you ensure more of your calls are captured and leveragedFaster ramp and more consistent coaching: insights from actual calls feed into Brevian’s knowledge engine3. What are the prerequisites?To set this up smoothly you will likely need:A Gong account with admin or technical-admin permissions (so you can generate API keys or enable access)A Brevian account with appropriate permissions (typically an admin or integrations owner)The correct Gong workspace(s) identified for ingestion (so you know which calls are included)Consent/compliance protocols in place (recording calls, permissions, privacy)Potentially CRM or telephony integrations configured (depending on your setup)4. How is the integration configured?While the exact workflow may differ, the typical steps are:In Brevian: navigate to Settings → Integrations (or equivalent) and select Gong.In Gong: generate the required API key/access credentials or configure access for Brevian.In Brevian: enter/authenticate those credentials to link Gong.Choose import settings: e.g., which workspace(s) in Gong, which types of meetings (external vs internal), whether automatic ongoing ingestion or just one-time bulk import.Confirm mapping/configuration: what data flows (recordings, transcripts, metadata), how they map into Brevian (e.g., how participants are matched to users/contacts).Test the ingestion with one or two calls to confirm everything works.5. What data from Gong is imported into Brevian?Typical data flows include:Call recording and/or transcript from GongMetadata: meeting title, date/time, participants, duration, external vs internal attendeesPotentially key discussed topics or tags (if Gong captures those)In Brevian: this data becomes searchable, analyzable, and tied to the relevant account/deal/person so you can generate insights6. How often does the sync occur?Depending on your setup:You can choose bulk import (one-time or periodic batches of historical calls)You can set continuous ingestion, meaning new calls in Gong are automatically pulled into Brevian shortly after completionIf you add new workspaces, participants, or settings in Gong, you may need to manually refresh sync settings in Brevian7. Who gets access to what?Only users in Brevian with the proper permissions will see imported Gong data (you may configure which user roles can view/edit)Imported calls may be tied to specific accounts/deals so only relevant teams can access themIf Gong workspace includes internal calls/non-customer calls you may want to filter them out so sensitive data isn’t broadly visible8. What happens to participants from Gong calls that don’t match existing contacts/users?Typically, Brevian will attempt to match participants via email or user ID.If no match is found and if the setting allows, Brevian may create a new contact/person record (depending on your configuration) or simply import the call without creating new entities.It’s recommended to review mapping rules so you don’t get duplicate contacts or irrelevant records.9. What happens if a call fails to import?Common causes of failure may include:Missing or invalid API credentials/permissionsThe call is from a workspace or user not included in the ingestion scopeThe participant(s) don’t have valid email addresses or required metadata If a call fails: review the ingestion logs in Brevian, check the Gong workspace settings, confirm the API access, and ensure the filtering rules (e.g., only external customer-facing meetings) are correct.10. What about data privacy and security?Make sure your organization’s call-recording consent policies are in place for Gong.The integration inherits the security controls of both platforms—ensure only authorized users can access the imported recordings in Brevian.If your company has specific compliance needs (GDPR, HIPAA, etc.), verify that the data flow meets those requirements (storage, retention, access logging).Review where the recordings/transcripts are stored, how long they are retained, and who can export or share them.11. Can we filter which calls get imported?Yes. You can typically filter by:Workspace(s) in Gong (e.g., only the “Customer meetings” workspace)Meeting type (external vs internal)Duration or date range (e.g., only calls longer than X minutes, only calls after a certain date)Specific teams/users (e.g., only AEs in North America) Ensure your filtration rules are configured before enabling continuous ingestion for best results.12. Does this integration work with historical calls?Yes. You can import historic recordings from Gong into Brevian (bulk import), though:Importing very large volumes (months/years of calls) might take longer and need staging.You may want to archive or mark older calls differently to avoid clutter.After bulk import, you can switch to continuous ingestion for future calls.13. What about linking calls to the correct account or deal in Brevian?Make sure your CRM is integrated and/or call metadata includes account/deal information (e.g., via participants’ email domains or Gong’s deal associations).In Brevian, ensure your mapping rules align (e.g., email domain = company, deal ID = CRM field) so that calls are correctly attributed.Incorrect mapping can lead to orphan records or mis-attribution, so it’s best to test mapping rules early.14. How can my team get started and train effectively?Kick off with a pilot: select a subset of calls/users to import and review how the insights appear in Brevian.Provide enablement/training on how to use the imported call data: e.g., how to search, generate insights, coach using specific calls.Define usage best practices: e.g., tagging important calls, using call-based learning, referencing call insights in deal reviews.Monitor and iterate: as the team uses the integration, capture feedback and refine filters, mapping, and usage.15. Who should I contact if I encounter issues?For Gong side issues: check your Gong admin, workspace settings, API access, and call-recording settings.For Brevian side issues: contact your Brevian admin or support team.It’s also helpful to document logs (import errors, mismatches, missing participants) and escalate with both platforms, if necessary.16. Can I disconnect or disable the integration later?Yes. You can disable or disconnect the integration via the integrations/settings panel in Brevian. Once disconnected:New calls will no longer be imported from GongPreviously imported calls remain in Brevian unless manually removedIf you plan to reconnect later, you may need to re-authenticate and re-configure the ingestion filters & mappings17. What are the best practices for maximizing value?Ensure consistent call recording discipline in Gong (e.g., all customer-facing calls are recorded/transcribed)Set up the mapping and filtering rules thoughtfully so Brevian gets high-signal data (not internal chatter)Train your team to use call-derived insights in coaching, deal reviews, and strategy planningPeriodically audit the imported call data: check for orphan records, duplicate contacts, mapping errorsCombine call insights with Brevian’s other data sources (product knowledge, market signals, enablement assets) to drive richer conversation intelligence

## Permissions
Integration instructions here

- Call recordings and Transcripts — Push to Partner — Knowledge Graph

## Next steps
- **Authenticating User Requirements** — To authenticate and setup this integration for the first time, a user must be a Gong Tech Admin and have Admin permissions in Brevian 
- **Subscriptions Required** — Gong integration is available for all Brevian customers of every tier. Users should be customers of Gong and have an active Brevian Subscription. 

## Connect
Go to the Brevian App, and go to Integrations under Admin section in the side drawer.The page will list all the supported integrations.Click on the + icon near to Gong.Copy the meeting callback URL.Log into your Gong accountGo to Admin Centre in the drawerIf the option is not available, you may not have admin access. Please contact the owner to get proper access.Click on Automation rules in the Ecosystem sectionTo add new automation rule:Select New Call as Trigger(Optional) You can set filters for the trigger by clicking on the pencil ✏️ iconChoose Fire webhook as the ActionSet the URL copied from step 3 as the callback URLSelect Signed JWT header as the authentication methodClick on Show public key and copy the public keyGive an identifiable name and proper description to the ruleEnable the rule and save the changesGo back to the Brevian App, paste the public key, and click on Setup with OAuth 2.0.Login and authorize Brevian.If the authorization succeeds, you should be able to see a green tick mark ✅ next to Gong in the integrations pageYour meetings from last 3 months will be automatically imported to the Brevian App, and all the calls (that gets filtered in, if you’ve applied any filter) will also get imported as soon as they are finished.