Skip to content
Halo by OmniTrust

Optimize · App Connections

Available now· 1,000+ apps in the connection catalog

Connect agents to the apps your work lives in

Halo's connection catalog lists 1,000+ apps your agents can use, including Slack, GitHub, Jira, Microsoft 365, and Zendesk. Credentials stay bound at the gateway, and policy decides which actions an agent may take.

Book a walkthrough Start with Halo
apps in the connection catalog
1,000+
credential values once saved
Write-only

Why it matters

Each connected app widens what an agent can do

Agents become useful when they can read from and act in the systems where work happens. Each connection also carries credentials and permissions that need an owner and a limit.

  1. 01

    API keys pasted into agent settings are easy to copy, hard to rotate, and hard to trace.

  2. 02

    An app that allows many actions can give an agent more power than its job requires.

  3. 03

    Without a record, nobody can say which agent used which connection and when.

Capabilities

Connections with limits attached

Connections run through the Halo gateway, so identity, policy, approvals, and evidence apply to the apps an agent uses.

  • Connection catalog

    Browse 1,000+ apps in the Halo connection catalog, including Slack, GitHub, GitLab, Linear, Jira, Notion, and HubSpot. Available actions vary by app.

  • Scoped access

    Grant an agent only the apps and actions its job needs, such as reading metrics or posting messages.

  • Brokered credentials

    Credentials are stored write-only and bound at the gateway. Agents receive scoped capabilities and never see raw keys.

  • Policy on app actions

    Policy bundles evaluate the tool, its arguments, and the destination, so a rule can, for example, allow reads and hold sends for approval.

  • Approvals for sensitive actions

    Pause higher-impact actions, such as posting externally or changing a record in a system of record, until a person approves.

  • Usage and evidence

    Gateway decisions attribute connection use to the agent and record it in the evidence trail, so reviewers can see which agent used which app.

How it works

From catalog to governed use

The four steps are the same across apps, and available actions vary by app.

  1. 1

    Pick the app

    Choose a connection from the catalog and review which actions are available for it, since actions vary by app.

  2. 2

    Authorize access

    Provide the credential or authorize the connection. Halo stores the value write-only and binds it at the gateway.

  3. 3

    Scope and govern

    Select the actions an agent may use, and add policy and approval rules for the sensitive ones.

  4. 4

    Use and review

    The agent calls the app through the gateway. Decisions are recorded, and the credential stays at the gateway.

Named apps

From chat to code to support queues

The catalog spans collaboration, developer, work management, support, data, observability, and payments apps, including Slack, GitHub, Linear, Zendesk, Snowflake, Datadog, PagerDuty, and Stripe. Available actions vary by app, so check the actions you need.

  • Collaboration with Slack and Microsoft 365
  • Developer tools such as GitHub and GitLab
  • Work management in Jira, Linear, and Asana
  • Support and CRM with Zendesk, HubSpot, and Intercom

FAQ

Questions, answered

The Halo connection catalog lists 1,000+ apps. Available actions vary by app, so a connection to one app may support actions that another does not. Check the actions you need before you plan a workflow around an app.

Halo stores connection credentials write-only and binds them at the gateway. Agents receive scoped capabilities for approved work and never see raw keys. After you save a value, Halo does not display it again.

Yes. Grant access to specific apps, then use policy to allow, deny, or hold actions by tool, arguments, and destination. Higher-impact actions can pause for a person to approve, and the decision is recorded.

Tool calls, including MCP tool traffic, pass through the Halo MCP and tool gateway. The gateway applies identity, policy, approvals, budgets, and evidence, whichever app an agent calls. Credentials for each connection stay bound there.

Plans differ. The Individual plan includes up to three app connections, and the Professional and Team plans include unlimited app connections. Enterprise terms are agreed with our team. Check the pricing page for current plan details.

Related capabilities

MCP and Tool GatewayGovern MCP servers and tool callsLearn more about MCP and Tool GatewayHalo AgentsLaunch secure agents in minutesLearn more about Halo AgentsHuman ApprovalsPut people on high-impact actionsLearn more about Human Approvals

Put a halo around the AI your business runs.

See discovery, runtime policy, approvals, and evidence working together on your own use cases.

Book a walkthrough Start with Halo