Skip to main content

​
What Zapier adds to Halo

The Halo Agents app for Zapier connects your workspace to thousands of apps without code. Zapier is available on plans that include API access (Pro and up).

​
Connect Halo

1

Add a Halo Agents step

In Zapier, create a Zap and search for Halo Agents. Pick a trigger (such as Ticket Escalated) or an action (such as Create Ticket).
2

Sign in and approve

Click Sign in. Halo asks you to sign in and approve what Zapier may do. Read access is pre-selected; tick the write scopes (inbox, contacts and companies, CS suite, workflows) you want your Zaps to use. The connection is named after your workspace.
3

Test and turn on

Map fields, test the step and publish the Zap. Turning a Zap with a Halo trigger on registers a webhook in Halo; turning it off removes it.
A connection acts as the person who connected it: actions can only do what that person can do in the dashboard, and revoking the connection in Halo (Settings → Integrations) stops its Zaps.

​
Triggers

Every trigger delivers the event as Halo sends it: event, occurred_at, actor and data, where data holds the record under its object name (for example data.ticket.status, data.contact.email, data.deal.stage.name) and the event’s own fields beside it (data.old_status and data.new_status on a status change, data.escalation_reason on an escalation, data.from_stage and data.to_stage on a stage change). While you set up a Zap, Test trigger loads your three newest records of that kind so you can map their fields.
Ticket Escalated is the trigger for paging: connect it to Slack, PagerDuty, Opsgenie or SMS and the on-call person hears about a hand-off the second it happens, with the customer, the company and the reason in the payload.

​
Actions and searches

  • Team members, agents, inboxes, pipelines and stages, workflows and statuses are dropdowns filled from your workspace. Choosing a pipeline narrows the stages to its own.
  • Updates change only the fields you fill in. An empty field never clears a value in Halo. The one exception is Assign Ticket: leave Assign to empty to unassign the ticket.
  • Custom fields take the field’s name and a value; on an update they merge into the stored values.
  • Records: map a ticket, contact, company or deal ID from a trigger or an earlier step, or let Zapier look it up with the matching Find.
Actions run the same tools the Halo MCP connector exposes, with the same validation, permission checks and audit log.

​
What Zapier can access

Write scopes are unticked by default on the consent screen. A connection without them can still run every trigger and search.

​
Building your own integration

The Zapier app is built on Halo’s REST API and webhooks, which any OAuth client can use the same way.