How Integrations Work
Each integration can do up to three things, and you toggle them per workspace from the integration’s detail page:- Ingest pulls data from the integration into Halo (contacts, companies, deals, transcripts, contracts).
- Actions lets the AI agent run functions in the integration (create a HubSpot deal, file a Linear bug, request a Stripe refund).
- Notifications sends alerts from Halo into the integration (most commonly Slack).
All Integrations
Every integration HaloAgents supports today, grouped by category.CRM & Support
HubSpot
Contacts, companies, deals, engagements, and four agent actions.
Intercom
Import contacts, companies, conversations, and tickets.
Communication
Slack
AI agent in mapped channels and the central notification sink.
Billing & Payments
Stripe
Customers, subscriptions, payments, and a refund approval queue.
Engineering
Linear
File bugs and feature requests, reply on tracked issues.
Meetings
Zoom
Sync meeting transcripts and recordings as knowledge.
Fathom
Sync meeting transcripts and attendee insights.
Documents
PandaDoc
Sync contracts and signer activity, auto-link by signer email.
Setting Up an Integration
1
Open the integrations marketplace
In the dashboard, go to Integrations in the sidebar (
/dashboard/integrations). Filter by the mode chips (Sync, Actions, Notifications) to find what you need.2
Connect
Click Connect on the integration’s card. OAuth integrations (HubSpot, Slack, Stripe, Linear, Zoom) open the provider’s consent screen. API key integrations (PandaDoc, Fathom, Intercom) show a form where you paste your key.
3
Choose modes
On the integration’s detail page, toggle Ingest, Actions, and Notifications. Defaults are sensible: Ingest and Actions on, Notifications off until you set them up.
4
Pick agent actions (if applicable)
For integrations with Actions mode, enable the specific actions per agent at AI Agents > [Your Agent] > Actions. See Agent Actions.
5
First sync
Hit Sync now to trigger the initial historical pull. The cron then keeps it incremental from there.
How sync works
The first connect always triggers a full historical sync. Subsequent crons are incremental.
Authentication
If credentials go bad, the integration shows an Auth error banner with a “Reconnect” link. Cron sync is automatically skipped while there’s an auth error.
Knowledge contributions
Some integrations contribute to your AI’s knowledge base, the data the agent searches at runtime:
What gets ingested can be filtered with Learning Rules. Stripe and Linear don’t contribute to knowledge: Stripe data is relational (used in prompts and segments), and Linear data lives in Linear.