SIGNL4 now includes a new app for connecting to ConnectWise Manage (“Manage”). This makes 2-way integration with Manage a breeze, and responding to service desk tickets can now be done conveniently via mobile app in SIGNL4. This blog article has all the important details.

What features does the integration offer?

The integration offers the following features:

• New Signls, i.e. notifications via push, SMS or call for new service desk tickets
• Display of all desired ticket details, such as notes or tasks
• Status updates of service desk tickets via the mobile app
• Setting a ticket owner when acknowledged in SIGNL4
• Adding notes to tickets via the mobile app
• Synchronization of status changes in ConnectWise to SIGNL4.
• Ability to set which tickets should be transferred to SIGNL4 (e.g. only certain priority, etc.)

How does the integration work?

The integration is based on the ConnectWise Manage REST API. SIGNL4 is a client application for this API and retrieves service tickets from it.

API access uses credentials of an API member, which must first be created in Manage (see below). The member, its location, business unit/department, and default board define which service tickets can be seen/retrieved by SIGNL4.

Generally, ConnectWise Manage on-premises or a cloud instance is supported. The Manage API version should be “2019.1” or newer.

What components are needed in Manage?

The connector app in SIGNL4 requires several items in Manage. All except the API member are automatically created by the connector app when it is first started in SIGNL4. The following table gives an exact overview and explains further details about required prerequisites in Manage:

Setup Step 1 – Create API Member in Manage

Follow these steps to create the API member in Manage:

1. Log in to ConnectWise Manage as an administrator
2. Click on “Members” in the menu under “System”
3. Now select the tab “API Members”
4. Click on “New Item”
   
5. Now set the following properties, among others:
   1. Member ID (example: “signl4”)
   2. Member Name (example: “Derdack SIGNL4”)
   3. Role ID: Admin
   4. Location
   5. Business Unit

   

6. Save the member and open the “API Keys” tab.
7. Click on “New Item”
8. Enter a name (example: “SIGNL4”) and save it.
9. Now copy the private key (it is no longer visible) and save it together with the public key, both will be needed in the next section.
   

Setup Step 2 – Configure connector app in SIGNL4

The following steps will now create the connector app in SIGNL4:

1. Log in to SIGNL4 as an administrator.
2. Select the team in the menu for which you want to create the integration and then click on “Apps”.
   
3. At the bottom of the page, under App Templates, select ConnectWise Manage and click “Create”.
   
   1. Instance URI:
      The root URL of your ConnectWise Manage instance without any additional path. An example is https://na.myconnectwise.net
   2. Company ID:
      Your ConnectWise Manage company id.
   3. API Member ID:
      The ID of the API member you created earlier in setup step 1
   4. Public API Key:
      The public API key from the API key you created for the API member in Mange
   5. Private API Key:
      The private API key from the API key you created for the API member in Mange
   6. Workflow Name – Triggering Signls:
      Name of the workflow rule that will be used for the ticket transfer to SIGNL4 (see above). A workflow rule with this name will be created in Manage if it does not exist.
   7. Workflow Name – Update Signls:
      Name of the workflow rule used for automatic closing of Signls in SIGNL4 (see above). A workflow rule with this name will be created in Manage if it does not exist.
   8. Workflow Name – Update CW Tickets:
      Name of the workflow rule that defines how tickets are updated when Signls are acknowledged or closed in SIGNL4 (see above). A workflow rule with this name will be created in Manage if it does not exist.
   9. Custom Field Retrieval:
      Name of the custom field that controls the service ticket retrieval by SIGNL4 (see above). A custom field with this name will be created in Manage if it does not exist.
   10. Custom Field Status:
       Name of the custom field required for automatic closing of Signls in SIGNL4 (see above). A custom field with this name will be created in Manage if it does not exist.
   11. Custom Field User:
       Name of the custom field required for ticket owner mapping (see above). A custom field with this name will be created in Manage if it does not exist.
   12. Owner assignment when:
       Select here whether or when the user who acknowledges or closes in SIGNL4 is to be set as the ticket owner in Manage. The assignment is done via email address, i.e. the email of the user in SIGNL4 must be identical to the email address of the user in Manage (“Office email”).
   13. Note options:
       When a SIGNL4 user comments on a Signl, these comments are added as a note to the service ticket. Choose the flags you want these notes to be assigned (e.g. make sure it is added as an internal comment, not visible to the customer, etc.).
   14. Additional details:
       Select which details that may be linked to a service ticket should also be retrieved and added to the Signl.
4. Once all fields are configured, click on “Create”.
5. On the details page that appears for the created app, click “Enable”.
6. After that, the connector app will connect to ConnectWise and then create workflow rules and custom fields.
   Therefore, it may take some time until the app is activated.
   

Done – ConnectWise Manage goes Mobile!

Once everything is set up and configured, you can now create a new service ticket in ConnectWise and then acknowledge, annotate and close it in the SIGNL4 mobile app. These actions are then synchronized back to Manage.