Skip to main content

​
Three modes

Every integration in Halo can support up to three modes. You toggle them per integration at the top of the integration’s detail page. Each integration declares which modes it supports. For example, HubSpot supports all three. Linear supports only Actions. Zoom supports only Ingest.

​
Ingest

Ingest mode pulls data from the integration into Halo’s database. Two flavors:
  • Relational ingest — data goes into Halo tables for use in prompts and segments. Examples: Stripe customers and subscriptions, Intercom contacts and tickets.
  • Knowledge ingest — data is also chunked, embedded, and searchable by the AI. Examples: HubSpot engagement bodies, Zoom transcripts, PandaDoc contract content.
Ingest defaults to on when unset. Sync runs in two ways: Disabling ingest stops both cron and webhook processing.

​
What gets ingested

Linear is the exception — no ingest mode. Halo tracks Linear issues it created (for reply behavior) but doesn’t pull existing Linear issues into the knowledge base.

​
Actions

Actions mode enables the integration’s tools for AI agents. When on, you can wire the integration’s actions to specific agents at AI Agents > [Agent] > Actions. Actions defaults to on when unset, but agents are still gated separately — even with actions mode on, an agent only has the action available if you’ve explicitly enabled it on that agent.

​
Available actions

Each action shows a destructive flag (red badge) if it mutates external state. Be deliberate when enabling destructive actions.

​
Why two layers

The two-layer design (workspace mode + per-agent enable) lets you:
  • Disable an entire integration’s actions when you need to (e.g. during a maintenance window)
  • Vary by agent — your sales agent might have HubSpot create_deal but not your support agent
  • Test new actions on one agent before rolling out

​
Notifications

Notifications mode sends events from Halo into the integration. Today, the primary notification sink is Slack — most integrations don’t define their own notifications mode but instead route alerts through Slack when both are connected. Notifications defaults to off when unset.

​
Slack notification types

When Slack notifications are enabled, you can subscribe to: Each type can be enabled or disabled independently. Notifications go to a default channel you configure (or per-rule channels for advanced setups).

​
HubSpot notifications mode

HubSpot has its own notifications mode that gates whether new_hubspot_engagement Slack notifications fire. With HubSpot notifications off, engagements still ingest as knowledge but don’t ping Slack.

​
Per-integration mode summary

​
Where to go next

Slack Integration

The notification sink for most other integrations.

Agent Actions

Enable specific actions per agent.

Learning Rules

Filter what gets learned from ingested integration data.