Integrations, Webhooks, APIs

We are working with Rewst for process automation. It'd be great to be able to uninstall agents via API, create/delete users, isolate machines, etc..

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

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.

I would like to receive notifications through Slack. Integrating Slack notifications would help me stay updated without having to check multiple platforms.

It is great that you integrate with our ticketing system, BMS, and can create tickets for us directly. What would make this even better would be a two-way communication where if the ticket is Resolved in BMS, the Incident or Escalation would also be resolved in Huntress Portal. After our techs take care of the tickets, they still have to come to the Huntress portal and resolve the issues here, creating twice the amount of work.

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.

Currently, it appears only a single organizational API key can exist at any given time. It would be nice to have the ability to generate multiple API keys and name them based on how they're being used. Related, having created, created by, expiration (optional), "last used" and "last seen" would be useful when managing multiple keys. This might also be a prerequisite to supporting a related request - scoping of API keys to specific tenants ( https://feedback.huntress.com/huntress-api/p/msp-breakdown-of-api-access ).

You now close tickets for incidents, but please can you also close automatically tickets for escalations and unwanted access when resolved.

An additional integration option for event updates that initiates a HTTPS callback and posts detailed JSON data about the event. It will allow faster response and wider range of integration options and much more preferable then having to parse an email.

We use monthly additions rather than open-ended ones which Huntress seems unable to support. This means I have to use N-Central's billing profile export to create an addition for an incorrect amount, and then have Huntress's billing Sync run the next day to then update the addition amount to the correct value. N-Ventral's billing profile exports aren't the most reliable, and I also don't like having to create these incorrect entries first, when Huntress could just do the whole thing directly and correctly.