Reporting Incidents to ConnectWise Manage PSA

Team: Huntress EDR
Product: ConnectWise Manage
Environment: Huntress Dashboard
Summary: Huntress can report incidents and step-by-step remediation instructions directly to your cloud-based and on-premise ConnectWise Manage PSA.

Update Dec 22, 2022: If you have previously set-up the integration with least privilege you will need to update the permissions to use the new features. The permission updates needed can be found at step 12.

Huntress can report incidents and step-by-step remediation instructions directly to your cloud-based and on-premise ConnectWise Manage. The ticket is created under the service board you specify. The ticket will be reported under the client's company name--Huntress uses the Organization Name to identify the Company Name within ConnectWise. 

1Creating a new security role

2Creating an API Member in ConnectWise Manage (does not count against your user licenses)

3Generating public and private keys for the API Member account

4Configuring the Huntress integration with the generated public and private keys

Creating a Security Role

1. Login to ConnectWise Manage using either the web or desktop version. 
   
   
   
2. In the lower-left corner of the ConnectWise interface, select the "System" section to expand its options.
   
   
   
3. Select the "Security Roles" sub-option. 
   
   
   
4. Click the + icon in the top-left of the Security Roles module

   
   
   

5. Enter a name for the new security role (e.g.Huntress API) and then click the Save icon.
   
   
6. You will be brought the Security Modules for Role screen.
   
   

7. Click the down arrows beside the Companies, Procurement, Service Desk, and System headings to expand each section.

8. In the following sections, modify the values in the table below
   

   Companies	Add Level	Edit Level	Delete	Inquire Level
   Company Maintenance	None	None	None	All

   Procurement	Add Level	Edit Level	Delete	Inquire Level
   Products	None	None	None	All

   Service Desk	Add Level	Edit Level	Delete	Inquire Level
   Service Tickets	All	All	None	All

   
   

   System	Add Level	Edit Level	Delete	Inquire Level
   Member Maintenance	None	None	None	All
   Table Setup	None	None	None	All

9. Required for Billing Integration: If you want to get more granular than ALL agreements, you can click "customize" and limit the permissions to just the one Agreement you will use
   

   Finance	Add Level	Edit Level	Delete	Inquire Level
   Agreements (customize)	None	All	None	All

   
   

   Procurement: 
   

   Procurement	Add Level	Edit Level	Delete	Inquire Level
   Product Catalog	None	None	None	All

   
   
   
10. Click on "customize" next to "Table setup
    
    
11. Disallow everything except “Company / Company Status,” “Service / Service Board,” “Service / Priority,” "Service / Source."
    
    
    
    

    Tickets will fail to send to companies that are any status other than "active." A lot of times the catch-all will be something like "not approved" and ticket creation will fail with the error "ticket object not found"

Creating an API Member account in ConnectWise

The name of the API user will be visible to your users. We recommend naming the API user to match your company brand. (e.g. "Huntress API"). See https://docs.connectwise.com/ConnectWise_Documentation/090/040/010/040 for more information. 

Huntress can report incidents and step-by-step remediation instructions directly to your cloud-based and on perimeter ConnectWise Service Boards. The ticket will be created under the service board you specify when configuring the integration. The ticket will be reported under the client's company name--Huntress uses the Organization Name to identify the Company Name within ConnectWise. 

1. Login to ConnectWise Manage using either the web or desktop version. 
   
   
2. In the lower-left corner of the ConnectWise interface, select the "System" section to expand its options. 
    
   
   
3. Select the "Security role" sub-option.
   
   
   
4. You'll now need to create a new API Member. To do so, select the "API Members" tab at the top of the newly opened Members pane.
   
   
   
5. Select the plus (+) sign on the left side of the Members pane to add a new API Member account.
   
   
6. In the New Member form, you'll need to fill out all required fields which are denoted with asterisks (*).
   
   
7. Populate the Member ID, Member Name, and Email fields. (The member ID is the User ID and the Member Name is the display name that will show on tickets)
8. Within the Role ID drop-down menu, select the Huntress API role that you created earlier. Leave other values as default (unless you have another use-case and understand how the options work). 
9. First, select the Default Board you would like to use for the Huntress API. Then, under Restrict Board Access select the Service Boards you DO NOT want the Huntress API to have access to (follow the least-privilege method, we suggest selecting all Service Boards Except for the one you want Huntress Tickets going to.
   
10. Congrats, you've populated all the needed fields! Create your API Member by clicking the floppy disk icon at the top of the Members pane.
    Do not return to the main Member pane. Proceed to the next section to continue.

Generating public and private keys for the API Member account

1. You'll now need to generate public and private keys for your newly created API Member. Start by selecting the "API Keys" tab at the top of the Huntress API pane.
   
   
2. Select the plus (+) sign on the left side of the Huntress API pane to add a new API Key.
   
   
3. Populate the Description field with "Huntress API Key".
   
   
4. Create your Public and Private Keys by clicking the save icon.
   
   
5. Congrats! You've successfully generated the API keys Huntress needs to create tickets. You'll need these in the next steps so don't navigate away frompage.

Setting up the Huntress Integration to ConnectWise

1. Login to the Huntress Dashboard.

   
   
   

2. Hover over the Huntress options menu in the upper-right corner of the dashboard.

   
   
   

3. Select the "Integrations" option from the menu.

   
   
   

4. Select the "Add" button to create a new integration.

   
   
   

5. Select the "ConnectWise Manage" banner.
   
6. Select the applicable location for your ConnectWise instance. Populate the "Company ID" field with your ConnectWise Company ID. Populate the "Public Key" and "Private Key" fields with the previously generated Member API Keys. Specify the name of the service board to report to in the "Default Service Board" with the name of the service board.
7. Select the "Add" button to save your integration.
8. Choose appropriate values for your environment and click Add when complete. If there is not a direct match, you will be left with a dropdown stating "Select a company" for you to manually match the Huntress Organization to the ConnectWise Company. Click Save.

If you are looking to update your existing mappings, simply log into your Huntress Dashboard, click "Integrations" under the hamburger menu and click the "pencil" icon next to your existing integration to update it.

The Default Company you set must be "approved," otherwise ticket creation for the default company (and test tickets) will fail.

The Service Board you are sending tickets to must have a default Status and must have a default Team Assignment configured in ConnectWise. See https://docs.connectwise.com/ConnectWise_Documentation/090/020/170/100/060 for more information.

If Huntress cannot match an organization, we will place the incident under a  Default Company you set here.

1. After adding your ConnectWise integration, Navigate back to Integrations. Huntress will attempt to make a connection to the specified ConnectWise Host.
2. Within a couple of seconds, the "Status" field should either change to a green ✔ or a red ✖.
3. If your connection was successful, congratulations! Huntress can now directly report incidents and remediation recommendations to your specified ConnectWise Service Board. If your connection failed, select the pencil icon to edit your integration settings. If you have any trouble getting this setup, don't hesitate to drop us a ticket.
4. You can test ticket creation and/or a billing sync with the "Test" buttons
   • Please note that you must have received at least one invoice for the billing sync to work