Leveraging the Huntress API in Power Automate
Nick Ross · · Video and write-up
Many of you may be using the native integrations within Huntress today to automate certain flows to your PSA tool like:
- Writing subscription information to agreements/contracts
- Creating tickets when new incidents occur
The Huntress API (opens in new tab) provides access to various endpoints that you can leverage for even more automation capabilities. In this article, I will show you how to set up Huntress as a custom connector in Power Automate so you can begin to create your own custom automation flows. You can get creative but here are some reasons why you would want to set this up:
- To chain more automation around when incidents occur
- To facilitate subscription information to 3rd party tools that Huntress does not integrate with natively today (Like QuickBooks)
- To aggregate subscription and device information across vendors.
I am currently using it to perform the aggregations:
This is a Power BI report in which we can see device information across vendors. I wanted see if there were any disparities between what is reporting out of Intune, our RMM, and Huntress. Additionally, I wanted to pull in subscription information so I can aggregate it at a customer level.
Prerequisites
- API Credentials with Huntress
- In the huntress portal, go API Credentials to generate a API Key and API Secret
- Premium Power Platform subscription.
- Licensing can get confusing here but I recommend one of the following: (Also you may be getting these licenses as part of your Silver or Gold Partnership with Microsoft)
The Steps
1. Go to https://make.powerautomate.com/ > Data>Custom Connectors>+New Custom Connector>Create from blank
2. You can upload the Huntress Logo and add the following info:
3. On the Security Page, select Basic Authentication. Add the labels of APIKey and APISecret. You will not add your information yet on this page, these are just labels:
4. For the Definitions, you will add the Endpoints you want to leverage in your Power Automate flows.
Follow the API documentation to add the correct request URL. You can add parameters as well too if you want. At a minimum, you might want to add the page parameter to facilitate pagination for endpoints that return multiple pages (which is very common with the API).
5. Go to the Test tab, click on + New Connection. Here you will enter your Huntress API Key and Secret
6. After the connection is entered you will be redirected back to the Test page. Here you can click on the refresh button to generate the connection you just created.
7. Finally, you can test the connection by selecting an operation and clicking Test Operation
8. If successful, you will get a 200 response.
9. Create the Connector
10. Now when you go to create a flow, you will have the Huntress connector as an option under Custom. All Endpoints you created under the Definitions section will be included
Happy Automating! For the full tutorial, check out my YouTube Video. Feel free to leave any questions or comments on the video:
See how your Microsoft 365 tenant measures up in about a minute.
CloudCapsule scans 300+ security controls, shows what to fix first, and keeps watching for drift after you fix it. Whether you manage one tenant or fifty, it’s the complete Microsoft 365 security workflow.
No credit card required. Results in about a minute.
Keep reading
Creating Tickets for Azure AD Risky Users | Power Automate
Many MSPs today track risky users across Azure AD if the customer has an AAD P1 subscription. These risk detections can often show a clear sign of breach based on impossible or atypical travel. One downside is that the controls with auto-remediation only come with a P2 license. We have some customers with this licensing […]
How I automated subscription renewal notices | Microsoft NCE
Microsoft New Commerce introduced a new level of liability because of their commitment terms and cancellation policies. On top of that they also introduced new operational complexity through subscription renewal dates which could be different for each customer in your environment if you did not move them to NCE on the same date. Microsoft has […]
Leveraging the Pax8 API in Power Automate
If you are an MSP working with Pax8 today, I believe you should be leveraging their API to automate workflows from a procurement and subscription management perspective. Many Pax8 partners don’t know Pax8 has an API but essentially it can be used at no additional cost and has the following endpoints: Customers Orders (Purchase net […]