SIGNL4

Mobile Alerting and Anywhere Incident Response

SIGNL4
  • Product
    • Feature Overview
    • On-Call Management
    • Mobile Alerting App
    • Why SIGNL4
    • First Steps
    • Security, Data Privacy & GDPR
    • Online Help & FAQ
    • Blog and what’s new
    • System Status
  • Use Cases
    • IT Alerting
    • SIEM & SecOps Alerting
    • IoT Service Alerting
    • Industry 4.0 Maintenance Calls
    • After-Hours Service Desk
    • Field Service Dispatching
    • Emergency Alerting
  • Integrations
  • Pricing
  • Company
    • About
    • Partner Program
    • Podcast
    • Media
    • Contact us
    • Newsletter
  • Free Trial
  • My Account
  • Deutsch

Inspiration

  • Home
  • Inspiration
  • General
  • 2-way integration with ConnectWise Manage

2-way integration with ConnectWise Manage

  • By René
  • January 12, 2021
  • GeneralIntegrationsUpdates
2-way integration with ConnectWise Manage

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:

TypeSample IDCreated byDescription
API Membersignl4ConnectWise
Administrator
Required for SIGNL4 to access the Manage REST API.

Required properties/values:

–          Location

–          Business Unit

–          Default Board

–          Role: Admin

–          API Key

Location, Business Unit and Default Board simultaneously define which service tickets can be retrieved by the connector app.

Custom FieldSignl4Retrieved_cConnector App (automatically)Tracking on the service ticket if it must be retrieved or has been retrieved

–          Not visible in the UI

 

Custom FieldSignl4Status_cConnector App (automatically)Required for automatic closing of Signls when corresponding service tickets change their status

–        Not visible in the UI

Custom FieldSignl4User_cConnector App (automatically)Required for assigning ticket owners

–        Not visible in the UI

Workflow RuleSIGNL4 – Trigger Signls Connector App (automatically)Defines which service tickets are retrieved. By default, all new tickets with the status “New (not responded)” are retrieved.

–        Must contain 3 event triggers (more information on request)

–        Can remain inactive (Invocation via Manage REST API)

Workflow RuleSIGNL4 – Update SignlsConnector App (automatically)Defines when Signls should be closed automatically (e.g. when the status of a ticket changes to “Closed (resolved)”)

–        Must contain 1 event trigger (more information on request)

–        Can remain inactive (Invocation via Manage REST API)

Workflow RuleSIGNL4 – Update CW TicketsConnector App (automatically)Defines how service tickets should be updated when acknowledged or closed in SIGNL4.

–        Must contain 2 event triggers with corresponding actions (more information on request)

–        Can remain inactive (Invocation via Manage REST API)

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.

 

Share

Related Posts

Alarm optimization – what SIGNL4 has to offer

December 21, 2022

Is being on-call a reason to quit?

September 21, 2022

Derdack Podcast: Efficient Service Delivery by automating your Incident Response

September 15, 2022

August 2022 Update – Change duty status of colleagues, configurable duty notifications and revised password change

August 17, 2022

Why SIGNL4?

SIGNL4® reliably notifies mobile operations teams and provides for a 10x faster response to critical alerts, major incidents and urgent service requests. Read more

 

Most Popular

  • Being a powerful ‘pager app’ SIGNL4 ca...
  • Microsoft Flow – send mobile Alert Notificat...
  • Geofencing Alerts with Automate or Tasker
  • Website Down Alert Notifications AWS CloudWatch Alarms to your mobile phone during...
  • Maintenance Call Machine Breakdown Maintenance Call using the AWS I...
  • Paging App Android settings for making SIGNL4 an even better...
  • Code Webhook CSharp C# C# code for the SIGNL4 webhook
  • Setting up the AWS IoT Button – and SIGNL4

FOLLOW US

  • Twitter
  • LinkedIn
  • Facebook
  • Vimeo

CATEGORIES

  • Communication (11)
  • Customer References (1)
  • Developer (11)
  • DevOps (12)
  • General (105)
  • Healthcare (1)
  • Integrations (24)
  • ITOM & ITSM (21)
  • Manufacturing (8)
  • OT & IoT (21)
  • Security (5)
  • Updates (32)

Tags

alert alert management alerts Android Application Insights Automate AWS IoT Button Azure B2B software c# Call Routing do not disturb Duty Scheduling emergency escalation Field Services geofencing handover Hotline ifttt Industrie 4.0 IoT IT Alerts IT Operations ITSM location Manufacturing Monitoring mute override on-call duty On-call Scheduling oncall duty Pager paging app press release SaaS splunk Tasker temperature voice voice recognition weather webhook Website zapier

ABOUT US

Derdack® is a long-standing innovator for enterprise-class mobile alerting and alert management solutions. Our global customer list includes The Boeing Company, Daimler, BMW, Porsche and many other leading brands. With SIGNL4® we have reinvented mobile alerting and alert management for operations teams in IT, IoT, Industry 4.0 and other areas where swift response to critical events matters.

SIGNL US

Phone +1 (202) 4 700 885
Intl +49 331 29878-20
CH +41 31 539 19 90
Email info (at ) signl4.com
Feedback online
Newsletter Sign-up

© 2023 - Derdack SIGNL4

  • Twitter
  • LinkedIn
  • Vimeo
  • GitHub
  • Feedback
  • About
  • Terms of Use
  • Privacy Policy (Website)
  • Cookie Policy (EU)
  • Product
    • Feature Overview
    • On-Call Management
    • Mobile Alerting App
    • Why SIGNL4
    • First Steps
    • Security, Data Privacy & GDPR
    • Online Help & FAQ
    • Blog and what’s new
    • System Status
  • Use Cases
    • IT Alerting
    • SIEM & SecOps Alerting
    • IoT Service Alerting
    • Industry 4.0 Maintenance Calls
    • After-Hours Service Desk
    • Field Service Dispatching
    • Emergency Alerting
  • Integrations
  • Pricing
  • Company
    • About
    • Partner Program
    • Podcast
    • Media
    • Contact us
    • Newsletter
  • Free Trial
  • My Account
  • Deutsch
Manage Cookie Consent
We use cookies to optimize our website and our service.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage vendors Read more about these purposes
View preferences
{title} {title} {title}