Integrations
The tools a finished qallin call hands off to.
Grouped by job, with what each one receives. Access is by waitlist, integrations included.
26
integrations
7
categories
4
things that leave every call
What an integration is
An integration is what leaves the call, not a logo.
Four things come off a finished call. Every tool below is where they land.
The directory
Every tool on the list, and what it gets.
Marked rows are asked for most — the same tally decides what gets added next.
CRM and sales
Calls, texts and what was promised land on the record you already work from.
- HubSpotAsked for mostCalls and texts logged on the contact, with the summary attached.
- SalesforceAsked for mostActivity written to the lead or the account it belongs to.
- PipedriveConversations attached to the deal they move.
- AttioEvery call on the company record, with the follow-up as a task.
- CCloseTwo-way sync for teams that already dial from Close.
Calendar and email
What the assistant books goes where your team already looks.
- Google CalendarAsked for mostA booked callback becomes an event on the right person’s calendar.
- GmailAsked for mostThe follow-up sends from your own address, with the call summary in it.
- OutlookThe same, for teams on Microsoft.
- Microsoft 365Directory sign-in, so joining is the account people already have.
Helpdesk and support
A phone call becomes a ticket instead of a note somebody meant to write.
- ZendeskMissed calls and voicemails open a ticket with the transcript in it.
- IntercomThe phone thread joins the conversation you already have with them.
- FrontShared inbox teams see calls in the same queue as email.
Accounting and payments
The quote agreed on the phone reaches the place it gets invoiced from.
- QuickBooksAsked for mostCustomers matched by number, so the caller is already the right account.
- StripeAsked for mostA payment link sent by text from the number they called.
- XeroThe same match, for teams on Xero.
Automation
For the workflow nobody but you runs.
- ZapierAsked for mostEvery call, text and promise available as a trigger.
- MakeThe same events, for teams building in Make.
- WebhooksAsked for mostRaw events to your own endpoint, signed.
- Public APIAsked for mostNumbers, calls, threads and tasks, documented.
Your own AI tools
Your own agent reads a finished call through the public API, on your own key.
- OpenAIYour agent reads the summary and the promise through the API.
- ClaudeThe same, for a team whose agent runs on Claude.
- GeminiThe same again, for teams already inside Google Workspace.
Where the team works
So a missed call is seen by somebody before the customer calls back.
- SlackAsked for mostMissed calls and new voicemails posted to the channel that owns them.
- Microsoft TeamsThe same alerts, for teams on Microsoft.
- NotionCall summaries written into the doc the team already keeps.
- Google SheetsA row per call, for the people who would rather have a sheet.
How this list is decided
Why this page has no “Install” button.
Access is by waitlist, so there is nothing to install into an account you do not have yet. Join the list and the integrations come with it — Team and Scale plans, the public API on Scale, prices not published.
The order they went in is a tally of what people ask for, not a roadmap. The same tally decides what gets added next.
Zapier, webhooks and the public API are rows in the list, not a developer band underneath. A workflow you build yourself still answers “does it work with what I run”.
The marks identify what we connect to. None of these companies is a customer or an endorser, and nothing here is drawn wearing another product’s interface.
Not on the list?
Tell us what you run. It moves up the queue, or gets put on the list.