Integrations, Webhooks, APIs

Currently Sonicwall firewalls (as well as Palo, Fortinet (etc)) show in the Huntress portal as "Syslog events for x.x.x.x", which can be frustrating if there are multiple firewalls using similar source IPs. Instead, it would be nice to have the option for them to be based on the " sonicwall.id " parameter which is the custom Firewall Name you set on the device (or atleast be able to manually rename the sources)

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.

Please add more functionality to the external recon. like: Darkweb monitoring Domains and Subdomains Domain Doppelgänger Social Media Accounts Blacklist checks for Mailserver Shodan / IntellX We're doing all this monitoring with external Tools or manually at the moment

Currently the Halo integration can create tickets/alerts but we cannot respond or close from Halo, Can this be expanded to a 2-way communication so our agents can work / close items in Halo instead of needing to close the Halo ticket and the huntress ticket separately.

Would like to see some sort of integration into Jira. Jira is a widely used service management tool and being able to route incidents, events, etc into Jira would be helpful for tracking purposes, esclations, etc. This is something that S1 can do today but their implementation is wonky.

Integrate with Syncro billing to update customer invoices with Huntress agent count.

Would be nice to be able to set who gets administrative types of notifications from Huntress. We have multiple administrators setup, who do not need all of the notifications of things, but need to be able to access the portal administratively.

I would like to have the ability to grant full disk access to Mac devices directly through the Ninjaone Policy. This feature would streamline the process and enhance security management for Mac users.

Trying to integrate escalations into our own system. I need the Subtype to come through on the output to determine which procedures to assign to an issue rather than just a Generic type such as "Microsoft 365 Login". The subtype is more useful to determine the actual issue at a glance such as "Login without Entra Usage Location". Its visible on the escalation page but does not return via the API. The other bits that would be nice would be the individual entity statuses. For example a single escalation can have multiple affected entities but 2 could already have been marked as resolved and 1 is not. I need this info to come back on the API as well.

Ability to map alerts to different Type / Sub-Type / Item depending on what the alert is for. E.g. If the alert has come from EDR vs MDR for 365