Skip to main content
Question

Issue with HALO integration

  • Oct 7, 2026 1:48 PM UTC
  • 1 reply
  • 38 views

Forum|alt.badge.img+1

We are trying to integrate with HALO. Our initial integration had some odd and concerning behavior, however.

The webhook configuration on the PagerDuty side is limited by scope to a specific service. However, when we enabled the integration on the HALO side it automatically upgraded priority to incidents assigned to OTHER services outside the scope of the webhook. 

We are trying to track down the issue, but I’m curious if others have experienced an issue like this.

1 reply

danieljcafonso
Forum|alt.badge.img
  • Community Manager 💚
  • Oct 29, 2026 10:48 AM UTC

Hey Christian! 👋

Thanks for posting this. Priority changes showing up on services outside your integration’s scope would worry me too, so let’s dig in.

I can’t speak to how things work on the Halo side, but here’s what I can share from the PagerDuty side, plus a few things that would help narrow it down.

Why the webhook scope might not cover this: a v3 webhook’s scope only controls which events PagerDuty sends out. It doesn’t limit what an external tool can change in PagerDuty. Any tool that updates incidents does that through the REST API, using whatever credentials it was set up with. If that’s a General Access API key, the key works across your whole account, not just one service. So something outside the scope you set could still end up changing incidents on other services.

A few things that would really help:

  1. Who made the change? Open one of the affected incidents and look at its timeline for the priority change. Who’s listed as making it? It could be a person, an API key, an integration, or an automation rule like Event Orchestration. This usually tells us straight away where to look. (No need to share incident IDs or customer details here, just who or what made the change.)
  2. What exactly changed? Was it the priority (P1–P5), the urgency, or the severity?
  3. Which credentials does the integration use to connect to PagerDuty? If it’s an API key, is it a General Access key or a User Token, and is it read-only or full access? You can see your keys under Integrations > Developer Tools > API Access Keys.
  4. When and how much? Roughly how many incidents and services were affected? Did it happen once, when you switched the integration on, or is it still happening?

If you need it to stop while you investigate: you can disable the API key the integration uses, from that same API Access Keys page. That blocks anything using that key from making changes in PagerDuty, and you can turn it back on later without recreating anything.

If the timeline points back to the integration’s key, it’s also worth reaching out to Halo’s support team, since they’ll know best what their side is sending over.

Let us know what you find and we’ll go from there!

Have a rest of a great day!