Matt

SIGNL4 uses the Freshservice REST API (https://api.freshservice.com/) to read ticket data or linked entities (e.g. retrieving the name of a department a ticket belongs to). Read through the next se...

When you create a new connector app instance in any of your SIGNL4 teams, you can configure some parameters or you leave it with the default values. In any case there is two fields that you need to...

Setup Step 1 - Create API Member in Manage Follow these steps to create the API member in Manage: Log in to ConnectWise Manage as an administrator Click on "Members" in the menu under "System" Now...

The flexibility of the SIGNL4 webhook makes it the most powerful one worldwide because it can receive an enormous number of content types and at the same time does not prescribe a fixed schema for ...

With setup step 1 you have created a service principal in Azure that is used by the connector app when accessing Azure APIs. The service principal credential data consists of the following and must...

After you have obtained the required Freshservice API key in setup step 1, you can now setup the connector app in your SIGNL4 team by following the instructions below. From the menu, choose the SI...

The Freshdesk connector app creates a new automation rule in Freshdesk automatically when it is started for the first time. You can find all the details about that automation rule in this article. ...

In case you do not want to assign the “Admin” role to your SIGNL4 API member user account, you can follow these steps to create a custom role for that user. The custom role only activates a minimum...

The SIGNL4 webhook can do more than just receive events to trigger Signls. For example, it can also update previously triggered Signls (status change) to keeps both systems in sync. Notified users ...

Data exchange between Freshservice and SIGNL4 is driven by Freshservice Automators. They control the following integration elements: Automator 1: Which tickets should be forwarded to SIGNL4 and w...