Integrations
Integrations connect Speechlytics to the systems where calls are recorded or reviewed. They remove manual uploads and can return completed insights to the originating platform.
| Provider | Direction | Behavior |
|---|---|---|
| FrontSpin | Inbound | Imports dialler recordings into Speechlytics. |
| Aircall | Inbound and feedback | Imports completed recordings and can write insights back to the Aircall call log. |
| HubSpot | Outbound | Logs processed calls and recordings on the HubSpot CRM timeline. |
Provider integrations are provisioned for your account by Speechlytics. Contact your representative to onboard a provider or rotate credentials.
Inbound recording flow
FrontSpin and Aircall use immediate event delivery plus scheduled synchronization:
provider call completes
↓
signed provider event
↓
recording queued for import
↓
audio preparation → transcription → enabled analytics
Scheduled synchronization acts as a backstop when an event is delayed or missed. Both paths use the provider's external call or recording ID to prevent duplicate calls.
An imported recording behaves like any other Speechlytics call. It can use preprocessing, sensitive-content protection, keyword matching, summaries, analytics, custom questions, and agent attribution.
Outbound HubSpot flow
After a call is processed, Speechlytics can create a HubSpot call activity, associate it with the matching contact, and attach or link the recording. The resulting HubSpot call ID is stored so repeated delivery does not create duplicate timeline entries.
Information needed for onboarding
The Speechlytics team will confirm the exact provider requirements. Typical inputs are:
| Provider | Typical requirements |
|---|---|
| FrontSpin | API access, webhook signing secret, and recording-access permissions. |
| Aircall | API ID, API token, webhook signing secret, and recording-access permissions. |
| HubSpot | Private-app access token, appropriate CRM and file permissions, and a recordings folder. |
Share credentials only through the approved secure channel. Do not place secrets in support tickets, documentation, source control, or client-side code.
Delivery behavior
- Provider events are acknowledged quickly and processed asynchronously.
- Repeated provider deliveries are safe because imports are deduplicated per account.
- Calls without an accessible recording are not imported.
- HubSpot export is idempotent for calls already linked to a HubSpot activity.
- Integration failures do not expose provider credentials in API responses.
Troubleshooting
When reporting an integration problem, provide the provider name, approximate call time, external call ID, account name, and whether the call exists in the provider.
| Symptom | Useful checks |
|---|---|
| A recording did not arrive | Confirm the provider completed the call and made the recording available. |
| A call arrived late | Immediate delivery may have failed and scheduled synchronization recovered it later. |
| A call appears twice | Confirm the provider did not assign different recording IDs to the same conversation. |
| Aircall has no returned insight | Confirm the imported call finished analytics and the source call still exists. |
| HubSpot has no timeline activity | Confirm a matching contact exists and the integration has the required permissions. |
Credential, event-signature, synchronization, and storage diagnostics are handled by Speechlytics support.