Skip to main content
Halo
Built by Halo AI. The connection is made from the Halo app via OAuth.

​
Start Here

Halo is an AI customer-success platform: support and sales agents, a shared inbox, and customer-success workflows. Connected to your Orbit workspace, it keeps your contacts and companies in step with Orbit, reacts to what happens in Orbit, and can act in Orbit from its own workflows. Halo also appears as a step in your Orbit workflows. Once connected, the Halo card on your Integrations page shows as Installed.

​
Key Features

  • Two-way contact and company sync: map Orbit fields to Halo fields and choose, field by field, which way each flows and which side wins when both changed
  • Forms and meetings in Halo: submissions and bookings become Halo contacts and timeline entries in real time, and Halo’s AI agents can book meetings on your scheduling pages
  • Orbit events start Halo workflows: a deal won, a lead qualified by AI, a tag added, a meeting booked or rescheduled
  • Halo acts in Orbit: Halo workflows can update a contact, add a tag, create a deal, task or note, enroll in a sequence, or run an Orbit workflow
  • Halo in your workflows: start a Halo workflow, update a Halo contact, send Halo an event or add a note as a step in an Orbit workflow
  • Secure OAuth: scoped, revocable access to your workspace

​
Setting Up the Integration

1

Connect from Halo

In Halo, open Settings → Integrations → Orbit and click Connect with OrbitForms.
2

Authorize via OAuth

You’re redirected to Orbit to approve the scopes Halo requests (listed below). Pick the workspace to connect and authorize.
3

Turn on the two-way sync

Back in Halo, under Two-way sync, review the field mapping and turn it on. Halo runs a first sync in the background: it links records that already exist on both sides (contacts by email, companies by domain) and adds the rest where you allowed it.
4

Verify in Orbit

Open Integrations → Halo in your Orbit dashboard. The card shows Installed once the connection is active.

​
What Halo can access

Halo never reads your passwords, API keys or other integrations’ credentials.

​
How the two-way sync works

The mapping table lives in Halo. Each row pairs an Orbit field (built-in or custom) with a Halo field and sets:
  • Direction: both ways, Orbit → Halo (Orbit is the source), or Halo → Orbit
  • When both change: Orbit wins, Halo wins, or the latest change wins
A change on either side reaches the other within about a minute. Halo ignores the changes its own writes cause, so the two systems never overwrite each other in a loop, and it reads your changes feed every 15 minutes to catch anything a webhook missed. Deleting a record in Orbit stops Halo writing to it; deleting it in Halo leaves the Orbit record alone. The full reference is in Halo’s Orbit documentation.

​
Using Halo in your workflows

With Halo installed, the workflow editor lists its actions under Installed apps in the add-step menu. They appear once the Halo AI app’s workflow actions are enabled and approved by Orbit; until then the menu doesn’t show them. The contact is the one the two-way sync linked, else the Halo contact with the same email, else a new Halo lead. Each run reports halo_contact_id as an output for later steps.

​
Disconnecting

  • From Halo: disconnect under Settings → Integrations → Orbit. Halo removes its webhook subscription and revokes its access; the card here flips back to Not installed.
  • From Orbit: remove Halo under Integrations → Halo. Halo’s tokens are revoked at once and Halo is notified: it turns its sync off and asks your Halo team to reconnect.
Contacts, companies and history already synced stay on both sides either way.

​
Troubleshooting

The status updates when Halo completes the OAuth flow. Refresh the Integrations page, and make sure you authorized the right workspace.
Halo shows the scopes it still needs on its Orbit page, with a Reconnect button. Reconnecting asks you to approve them.
Halo flags rows that couldn’t sync on its Orbit page, with the reason. A common one is a dropdown value Orbit doesn’t have as an option, or a custom field that was renamed or deleted in Orbit.
The steps appear only in workspaces where Halo is installed. Connect Halo from the Halo app first.
Disconnect from the Halo app, or remove Halo under Integrations → Halo.

​
Resources