Integrations

• Provider cards depend on your tenant’s integration configuration.
• Call importers require an audio-enabled package.
• Account or hybrid integrations must be connected by an account administrator or owner.
• User integrations must be connected or mapped for each user whose conversations should synchronize.

1. Open Settings → Integrations and select the provider category.
2. Find the provider card and click its connection action.
3. Complete the OAuth authorization or enter the API credentials requested by the provider-specific form.
4. When the form offers Test, verify the connection before saving.
5. After connecting, open Settings on the provider card to configure mappings, synchronization options, private numbers, campaigns, fields, or webhooks when supported.

Connect HubSpot from Settings → Integrations → CRM. User connections use HubSpot OAuth. Account connections use an administrator-managed Private App or service key.

• Grant access to the contacts, companies, deals, tickets, notes, and owners required by the features you enable.
• After an eligible external meeting is summarized, Meetric creates a HubSpot Note and associates it with matched contacts and companies.
• Optional settings can update existing notes, link deals or tickets, create missing contacts, enrich participants, and import deal or conversation-type data.

Create a Lime Go API key, then open Settings → Integrations → CRM → Lime, enter the key, click Test, and connect the integration.

After summary generation, Meetric matches a Person and Organization and creates a Signal containing participants, notes, the AI summary, and a link to the recording. Matching uses email first and phone second.

Obtain a Lime CRM API key and the base API URL for your instance. Open Settings → Integrations → CRM → Lime CRM, enter both values, click Test, and then Connect.

Meetric creates a History note after the AI summary is ready. The note is linked to the matching Person and, when available, Company. It includes meeting details, participants, notes, the complete summary, and recording and transcript links.

In Recman, open Settings → API Keys, create an active API key, and copy it. In Meetric, open Settings → Integrations → CRM → Recman, enter the key, connect, and click Test.

• Candidates receive an Interview; Company Contacts receive a Log.
• Contacts are matched by email, then mobile or office phone.
• Map each Meetric presenter to a Recman user so created records have the correct owner.

Obtain an IntraManager API key and API base URL. Open Settings → Integrations → CRM → IntraManager, enter the credentials, configure the available summary toggles, click Test, and connect.

When meeting summary delivery is enabled, the generated summary is added as a User Note on the relevant IntraManager profile. Accounts that support playbook daily summaries can enable that option separately.

Obtain your SuperOffice domain prefix, customer instance identifier, and token key. Enter them under Settings → Integrations → CRM → SuperOffice, click Test, and connect.

After summary generation, Meetric sends meeting details, presenter and participant emails, the summary, dates, meeting type, location when available, and a recording link to the configured SuperOffice integration. The recording itself remains in Meetric.

In Startdeliver, open Settings → API keys and create an active, unrestricted API key. Enter it under Settings → Integrations → CRM → Startdeliver, click Test, and connect.

• Meetings create an Interaction under Customer → History → Interactions.
• Contacts are matched by email first, then phone.
• Optional settings can create missing customers and contacts or create tasks from extracted conversation actions.

In TeamTailor, open Settings → Integrations → API keys and create an Admin API key with read and write access. In Meetric, open Settings → Integrations → CRM → TeamTailor, enter the key, click Test, and connect.

Externally recorded interviews can create a Partner Result on the candidate profile after the summary is ready. Candidates are matched by email or phone.

Ensure the connecting Salesforce user has API Enabled through a Profile or Permission Set. Open Settings → Integrations → CRM → Salesforce, enter your Salesforce domain when requested, complete OAuth authorization, and follow the package-install prompt shown by the integration.

Completed summaries can be added to the Salesforce Activity Timeline and associated with matching Contacts, Accounts, Opportunities, and Cases. Keep participant names, emails, and phone numbers current to improve matching.

Copy your Dynamics organization domain, then open Settings → Integrations → CRM → Dynamics 365. Enter the domain, click Connect, and approve access through Microsoft.

Meetric creates a Note on the matching Contact and, when available, its associated Account. Matching uses the primary email, then mobile or telephone number. The Note contains meeting details, the summary, and a recording and transcript link.

Open Settings → Integrations → CRM → Pipedrive, click Connect, sign in to the intended Pipedrive account, and approve access.

After summary generation, Meetric matches the participant to a Pipedrive Person and creates an HTML Note. When available, the Note is linked to the relevant Deal.

Obtain an Upsales integration token from an Upsales administrator or Upsales support. Open Settings → Integrations → CRM → Upsales and follow the connection form shown for your tenant.

Completed meeting summaries can be sent to matching Upsales customer records. Keep contact names, emails, and phone numbers current. The exact connection method and available synchronization settings depend on the Upsales application configured for your tenant.

Open Settings → Integrations → CRM → Zoho, click Connect, sign in to Zoho, and authorize the requested access.

After connection, eligible meeting summaries can be synchronized with matching Zoho CRM records. Available record links and synchronization settings are shown on the connected integration and depend on the Zoho application configured for your tenant.

Connect CRM Service from Settings → Integrations → CRM → CRM Service. Enter the CRM Service host (for example crm.example.com, without https:// or a path), username, and password, then click Test, and connect. An account administrator or owner must complete this connection.

• When summary activity creation is enabled, Meetric posts the AI summary as a held CRM Service activity (Meeting or Call) linked to matched contacts and, when available, their related accounts. Each meeting creates one activity with the meeting name, summary, start and end time, and a recording link when available. Existing activities are not updated on re-sync.
• Contacts are matched by email first, then phone number. Optional user mappings assign the correct CRM Service owner.
• When participant enrichment is enabled, Meetric can fill missing participant name, email or phone, and company or account name from a matching CRM Service contact.

In Adversus, open the user page, select API access, and create an API user with the required access. Copy its API key and secret. In Meetric, open Settings → Integrations, select Adversus, enter the credentials, and enable call import.

After connection, use Adversus settings to configure user mappings, campaigns, import rules, variables, and AI fields when those sections are available for your account. Each campaign can optionally have a default user so calls without a normal user mapping are still assigned correctly.

An Aircall administrator must generate or retrieve the Aircall API ID and API Token. Open Settings → Integrations → Call Importers → Aircall and enter the credentials shown by the connection form.

Aircall is connected once at account level. Calls are imported for active Meetric users that are mapped to an Aircall user. If a call is missing, first verify that its owner is active and correctly mapped.

Dstny requires an Advanced Call Recording license and a call-recording super user. In the Dstny portal, open Config → Advanced → System Settings → API, create the API token, and note the super user ID.

Open Settings → Integrations → Call Importers → Dstny and enter the requested account credentials. After connecting, map Meetric users to their Dstny identities in the integration settings.

Flexfone requires a Call Recording license and customer consent. Ask Flexfone to provision the integration credentials, including the CVR and account identifier.

Open Settings → Integrations → Call Importers → Flexfone and complete the provider-defined connection form. After connecting, review user mappings before relying on automatic call import.

Open Settings → Integrations → Call Importers → Infracom. Enter the credentials requested by the connection form supplied for your tenant, then connect the integration.

Open Settings → Integrations → Call Importers, select Enreach Voice, enter the integration username and secret key, and connect.

After connecting, configure user mappings and copy the generated webhook credentials from the integration settings.

https://api.dev.acceptflow.com/api/v1/webhook/enreachvoice/calls

Connect Lynes under Settings → Integrations → Call Importers. Open its settings, choose the minimum call duration, and copy the generated Webhook URL and Webhook token.

1. In Lynes, open Phone System → Call Recording → Integrations.
2. Create a call-recording integration using API version 2.
3. Enable stereo, disable CI summary sync, and select the users or answer groups whose recordings should be sent.
4. Paste Meetric’s Webhook URL and use the Webhook token for authorization, then save.

Telavox uses a user-scoped token. Each user opens My account → Username → Handle keys in Telavox, selects Custom integration, and copies the generated token.

In Meetric, open the Telavox connection under Settings → Integrations → Call Importers, enter the user token, and save. Repeat the process for each user whose calls should be imported.

Connect Telink under Settings → Integrations → Call Importers, then open its settings and copy the Webhook URL and Webhook token.

In Telink, open Settings → Company → Telephony system → Call recording → Call recording integrations, then enter the webhook details. Send the token as Bearer Authorization when configuring the integration.

Tele2 requires an Advanced Call Recording license and a call-recording super user. In the Tele2 portal, open Config → Advanced → System Settings → API and create the API token.

Connect Tele2 under Settings → Integrations → Call Importers, enter the requested account credentials, and configure user mappings in the connected integration.

Teleproffs Go uses the Dstny-style account connection. It requires an Advanced Call Recording license, a call-recording super user, and an API token created under Config → Advanced → System Settings → API.

Select Teleproffs Go under Settings → Integrations → Call Importers, connect the account, and map Meetric users to their provider identities.

Teleproffs One uses the Telavox-style user connection. Each user creates a custom-integration token under My account → Username → Handle keys in the provider portal.

Select Teleproffs One under Settings → Integrations → Call Importers, enter the user token, and save. Repeat for each user whose calls should be imported.

Telia requires an Advanced Call Recording license and a call-recording super user. In the Telia portal, open Config → Advanced → System Settings → API and create the API token.

Connect Telia under Settings → Integrations → Call Importers, enter the requested account credentials, and configure user mappings in the connected integration.

Create a Meetric-specific user in S2 and copy its Access Key and Secret Key. Open Settings → Integrations, select S2, and enter both credentials in the connection form.

After connecting, configure user mappings and any available campaigns and field mappings in the S2 integration settings. A mapped user is required for dialer access.

1. Confirm the conversation summary finished processing.
2. Confirm the CRM connection still shows as connected.
3. Check that the external participant has a matching email address or phone number in the CRM.
4. Review provider settings for summary creation, contact creation, deal linking, ticket linking, and user mapping.
5. If support is needed, provide the conversation link, the expected CRM record link, and the affected user.

1. Confirm the call was recorded by the provider.
2. Confirm the call owner is active in Meetric and mapped to the correct provider user.
3. Check the configured minimum call duration and provider-side recording selection.
4. For webhook integrations, verify the Webhook URL and Bearer token and confirm the provider is sending the selected recordings.