Integrations

Autotask Ticket Number is what is seen by internal users and clients in an Autotask ticket or in the portal. The Ticket ID# is ONLY visible in the URL for a ticket and is an internal only reference number. The current API integration puts the Ticket ID# as a comment in the Incident, which is not useful since there is no place to look that up in Autotask. This really should be the Ticket Number.

We use Autotask PSA and escalations (primarily for ITDR) get created as tickets in PSA which is great but our techs tend to live in Autotask, work the ticket, close it and forget to resolve and close the escalation within the Huntress portal which means we need to retroactively clean up a lot of old escalations. If we had two sync settings to auto close the escalation in the Huntress portal once the Autotask ticket is closed, that would make operations a lot smoother. Including a separate incident report two way sync setting option could be beneficial too.

Like what is currently available for DNSFilter, it would be great to have an integration for NextDNS. They have a public API, so collecting logs should be relatively straightforward.

Edge Connectors let third-party services authenticate, analyze, and report on browser events and usage data, providing valuable insights and smarter decision-making. https://blogs.windows.com/msedgedev/2025/04/28/introducing-edge-for-business-security-connectors/

Please add native integration with Microsoft Teams Workflows for Huntress Labs to send EDR and ITDR notifications directly to Teams channels. This would allow IT and security teams to receive real-time alerts within their existing communication platform, improving response times and reducing the need to rely solely on email or the Huntress dashboard—especially when technicians are mobile or onsite. Ideally, the integration should support the same notification format currently used for email and ConnectWise PSA, with options for channel targeting via Teams Web Link. Best Case Scenario: For IT teams that are constantly onsite or in the field, email alerts can be easily overlooked or delayed due to limited inbox access. A Teams integration ensures alerts are delivered as instant, high-visibility messages where technicians are already collaborating—resulting in faster acknowledgment and resolution of critical threats.

Ability to create email integrations at the organization level so incident reports for certain organizations will be sent to them and not the account level emails.

We would like to see a billing integration between Huntress and HaloPSA. Ideally this would push license counts for all Huntress products (EDR, ITDR, SAT, SIEM) to each of our customer records in HaloPSA and allow us to link the invoice quantities with licenses in use.

It would be nice to have an integration with NinjaOne US.

I would like to see an integration that allows the Huntress activity and logs to be connected as a log source to a SIEM. This would allow a 3rd party SOC to work with events as well.

I don't have any clients who use Windows Defender. It would be great if in the future there was a Sentinel One integration to pull logs from and review detentions to confirm that Sentinel One completely removed the threat.