Integrations in the web app
What the static image should show: The tenant app shell with Connectivity (Phone numbers, Telephony) and Admin (API keys) visible, matching a Pro tenant. Redact internal names if needed.
This help center is factual to the Callaro web application. The product does not ship an in-app wizard named “Connect HubSpot,” “Connect Salesforce,” or “Connect Zoho.” Use this article for what you can do in the UI; use your technical implementation notes for API keys, webhooks, and server-side integration patterns.
Where “integration” shows up in the app
| Area in the UI | Where to find it | What it is for |
|---|---|---|
| API keys | Admin → API keys | Manage tenant (or org-scoped) API keys the Public API uses. Gated for users who may manage API keys. |
| Phone numbers | Connectivity → Phone numbers | Numbers, pools, and assignment — outbound capacity lives here with campaigns. |
| Telephony | Connectivity → Telephony | Create and edit telephony connections (provider configuration, health, capacity). |
| Call logs | Monitor → Call logs | Filters and debug presets include webhook-related session fields (e.g. sessions that called a post-call webhook or had webhook failures) when the backend exposes those filter attributes. |
| Call detail — Webhooks | Open a session from Call logs (two-pane detail) | The Webhooks rail shows inbound webhook logs, pre-call / post-call delivery metadata, and error expansion when the backend returns metrics. Empty state: “Pre-call API and post-call webhook logs appear here when webhooks are configured.” |
| Getting started | Getting started page, or the checklist on Dashboard | Onboarding checklist — steps auto-complete when detected. Not a “CRM connect” list. |
| Partner integrations (partners) | For partner orgs, where the app lists partner integration credentials | Partner integration credentials (API/stream style configuration). Not the same as tenant “CRM” OAuth screens. |
What this section slot should show: A screenshot of Call logs with the filter bar or a webhook-related preset visible, or the Call detail header with the session id — whichever best illustrates “finding integration-related data in the list.”
What the GIF should show: (A) Call logs list with a webhook-related preset or filter applied, or (B) Call detail, Webhooks tab selected, one section expanded. Under ~8s loop.
What the video should show: Chapters: API keys (list only, do not show secrets) → Telephony connections list → Call logs (optional) → a completed Call detail with Webhooks visible. 1440×900, narrated or captioned.
User guides that match the app
What this section slot should show: API keys list (keys redacted) or Telephony connections list — a concrete screen that pairs with the bullets below.
- What gets logged (in the app) — call record, transcript, webhooks in Call detail
- Telephony connections in the app: go to Connectivity → Telephony. A dedicated end-user article can be added later when needed.
Technical implementation
- Public API, webhook, and integration patterns live outside the Help Center user-guide sync.
- Keep this article focused on in-app screens and operational guidance.
Replaced “CRM connect” articles
If you followed an older link: Connecting HubSpot / Salesforce / Zoho and Using Zapier in this user-guide space were not grounded in the current web app. They now carry a short deprecated notice. Use this article and technical implementation notes instead.
- Connecting HubSpot (deprecated)
- Connecting Salesforce (deprecated)
- Connecting Zoho (deprecated)
- Using Zapier (deprecated)