Autotask Billing (Beta) integration

Team: Huntress EDR
Product: Autotask PSA
Environment: Huntress Dashboard
Summary: This guide details the process of integrating Huntress with Autotask, including the steps required for setup and the operational mechanics of the integration.

The goal of this integration is to facilitate the transfer of agent and identity counts from Huntress to Autotask's Recurring Service Contracts. For it to work, these contracts must already be established in Autotask with designated services. Users have the flexibility to configure the integration for either daily or monthly execution. At present, the products from Huntress that are supported by this setup include EDR and M365.

This is presently in a BETA phase, so you'll need to reach out to our support team to get this feature activated. We welcome any feedback on issues or questions you may have!

Setting up Autotask correctly:

To initiate the billing integration with Huntress, it's essential first to ensure Autotask is correctly configured. This requires the establishment of Services and the corresponding Recurring Contracts.

Set up Autotask Services:

1. Navigate to the Features and Settings page in the Autotask Admin:
   
2. Click on Services within Products, Services, & Inventory
3. Click on New and go through the wizard. In the billing section, you most likely want to set the period_type to monthly since that's how Huntress bills. You can set the unit price to whatever your Huntress price is or leave it as zero. You’ll need one service for each Huntress product you are using.

Set up Autotask Contracts

1. From the hamburger menu, select Contracts:
2. Click on New and select Recurring Service Contract.
3. Navigate through the wizard. Associate the contract with a specific Account. You’ll need one recurring service contract for each Huntress organization mapped in autotask. For setting up recurring contracts in Autotask, they must have defined start and end dates. You can choose today's date as the start, and consider setting the end date to coincide with the expiration of your agreement with Huntress. The start date cannot be in the future. Within the wizard's Service section, you should include the services related to your Huntress products

Please note that Huntress will sync only the unit counts without including any costs or pricing information. With the services and contracts now prepared in Autotask, the next step is to configure their mapping within the Huntress portal.

Setting up the Huntress → Autotask Billing Integration

1. Navigate to the integrations page in the huntress portal and create an Autotask integration.
2. Enter your credentials and navigate through the setup. Once you’re on the configuration page, you will see a Billing tab where you can turn on the billing integration.
3. Enable the billing integration and map your Huntress Products to Autotask Services. Choose a sync frequency, which can be either daily or monthly. If selecting monthly, you must also specify a particular day each month for the synchronization to occur.

Once the billing synchronization is activated, it's essential to associate your Huntress products with corresponding services in Autotask. Currently, only EDR and MDR for M365 are compatible with this feature.

       4. The last step is to map your Huntress Organizations to recurring contracts with Autotask. The dropdown of contracts will only populate with Recurring Autotask Contracts.

For organizations to appear in either mapped or unmapped tables, they first need to be linked to accounts in Autotask under the mappings tab. If you don’t see organizations in this table, ensure they are first mapped to auto-task accounts.

Testing the integration.

Once you’ve turned the billing sync on, mapped Products → Autotask Services and Organizations → Autotask Contracts, you’re all set. The next step is to run the billing sync and test. Simply click the Sync Now button to queue the sync in the background:The synchronization process should complete within a few minutes. After it does, you can refresh the billing tab page to see the updated results displayed at the bottom.The table will show the synchronization results for each organization/product combination, allowing you to see when the sync occurred and whether it was successful. If a sync fails, a message will attempt to explain the reason. However, Autotask's API may return a vague "Internal Server Error," requiring further investigation with our support team.

Common issues include Autotask Services not being linked to the Contracts or the API User lacking the necessary permissions to access Services and Contracts. These are typical challenges that may need addressing to ensure successful synchronization.