Skip to content

Integrations

The Integrations catalog connects MiaRec to external platforms: telephony integrations bring conversations into the platform through vendor APIs, and single sign-on integrations let users sign in with an external identity provider. This page covers catalog administration and the synchronization jobs at concept level — platform-specific setup lives in the dedicated integration guides.

Where: Administration › System › Integrations. The catalog shows integration cards filtered by All / Single Sign-On / Telephony tabs, with a tenant filter and text search. Each card shows its connection count (or "Not connected") and a View settings link; Add registers a new connection.

Catalog and connections

An integration is a platform entry in the catalog; a connection is a configured instance of it — typically one per tenant (a card can hold several connections for different tenants). Opening a card lists its connections, where you can view, edit, and test each one. Some integrations can also be registered as tenant-scoped catalog entries visible to a single tenant.

Which cards appear depends on the build and the enabled feature flags — do not expect an identical catalog on every deployment. Typical entries include Microsoft Teams, Twilio, Webex Native Recording, and a generic "Other phone platform" card on the telephony side, and Google, Microsoft, and Webex on the single sign-on side.

Telephony integrations

Telephony integrations come in two shapes:

  • Recorder-based — the platform delivers media to the MiaRec recorder (for example, Microsoft Teams via SIPREC). The catalog card handles platform authorization and provisioning; capture itself goes through recording interfaces and recording rules.
  • Sync-based — MiaRec pulls completed recordings from the platform's own recording service on a schedule (for example, Twilio or Webex Native Recording). Each pull runs as a recurring synchronization job.

Synchronization jobs

Sync-based integrations create jobs such as Twilio synchronize calls, Webex Native Recording synchronize calls, and NICE InContact synchronize calls. They appear in the jobs console like any other job — schedule, runs, processed-record counts, and logs — which is where you monitor and troubleshoot syncing. See Jobs console and the job type reference.

Synced recordings become regular conversations and enter the same processing pipeline as recorded ones. Attribution to tenants and users relies on the integration's user linking and on extension matching — see Tenant configuration.

Single sign-on integrations

SSO cards (Google, Microsoft, Webex) enable the corresponding sign-in button on the login page and account linking for users. SAML identity providers are registered separately under Administration › User Authentication — see SAML. The customer-facing view of SSO is covered in Single sign-on in the Administration Guide.

Platform-specific setup

This guide does not repeat per-platform setup steps. Use the dedicated guides: