Freshservice integration with xMatters Connector enables IT service management teams to associate and sync the incidents and notes/conversations in xMatters with incidents, service requests, and notes/conversations in Freshservice, allowing real-time bidirectional updates between both the platforms. This ensures that updates in one application are automatically reflected in the other and vice-versa.
This article contains the following topics:
- Prerequisites for integration
- Install the app
- View dashboard
- Set up available recipes
- Manage available recipes
- Customize recipe
- Configure widget settings
Prerequisites for integration
Ensure you have the following, as part of the prerequisites for integration:
An active xMatters account.
Account administrator privileges within Freshservice to initiate the integration.
Manage Account privileges within Freshservice to start and stop recipes.
Install the app
To install the app:
Go to Admin > Automation & Productivity > Extensibility > Connector Apps.
Select xMatters Connector App from the Connector Apps list.
Click Install. The Configuration page opens.
Ensure that your Freshservice API Key is enabled before initiating the installation. Click Next.
Note: The Domain URL and API Key fields are auto-populated.
Enter the relevant xMatters connection details in the Client ID, Username, Password, and Company name fields. Then, click Connect.
(After the connection is established successfully) Click Next on the Connect xMatters tab.
Enable the Alerts toggle, if you want to receive email notifications on any errors that are detected within the configured recipes.
Enter the recipient email id(s) in the Email ID field.
Then, click Install.
View dashboard
The Overview page of a connector app includes the Dashboard and Dependency graph tabs.
The Dashboard helps you understand the total number of tasks you've consumed (this is the basis for your app usage billing), and also provides a consolidated graph view of the number of recipes, successful jobs, and failed jobs for all recipes.
To view the dashboard and dependency graph:
Go to Admin > Automation & Productivity > Extensibility > Connector Apps.
Click xMatters Connector App. The Configure xMatters Connector dialog opens.
Click Got it. The Overview page opens.
Note: Use the Period, Project, All recipes, Service/App, and Tag filters to modify the graph view. You can also sort and view the required data in a tabular format (below the graph), and view your plan usage and connection details on the Dashboard tab.
Go to the Dependency graph tab to view the dependencies in a grid layout.
Click on any icon to view all dependencies, such as Connection, Recipe, API Endpoint, and so on.
Note: Use the Asset, App, and Recipe status filters to modify the grid view.
Set up available recipes
To set up the available recipes:
Go to Admin > Automation & Productivity > Extensibility > Connector Apps.
Click xMatters Connector App. The Overview page opens.
Click Recipes. The Recipes page shows you the list of available recipes for the xMatters Connector App.
List of all the available default recipes
The following default recipes are available with the Freshservice and xMatters Connector integration.
Manage available recipes
You can preview, edit, start, test, or stop the available recipes.
Preview recipe
On the Recipes page, click Preview next to the recipe you want to view. The selected recipe’s preview page opens.
The Preview page includes the Recipe, Jobs, Connections, Versions, and Settings tabs.
On the Recipe tab, you can view various steps with pre-configured triggers, actions, and conditions.
Go to the Jobs tab to view all the jobs associated with this recipe.
Note: Use the Repeat job, Cancel job, Search jobs, All statuses, All types, and Period filters to modify or update the Jobs list.
Go to the Connections tab to view all the associated connections.
Go to the Versions tab to view all the associated versions.
Note: Use the Compare versions, Search version comments, All periods, All change types, and All collaborators filters to modify or update the Versions list.
Go to the Settings tab to view the usage metrics, dependencies, and concurrency associated with this recipe.
Start recipe
To start any recipe:
On the Recipes page, click Start next to the recipe you want to start.
Or, click Preview next to the recipe you want to start. Within the recipe preview page, you will find an option to start the recipe.
Edit recipe
To edit any recipe:
Click Preview next to the recipe you want to edit. The selected recipe’s preview page opens. If the recipe is active, click Stop. Then, click Edit.
Or, click the ellipsis icon next to a recipe on the Recipes page. Then, click Edit.
Stop recipe
To stop any recipe:
On the Recipes page, click Stop next to the recipe you want to stop.
Or, click Preview next to the recipe you want to stop. Within the recipe preview page, you will find an option to stop the recipe.
Test recipe
To test any recipe:
On the Recipes page, click Preview next to the recipe you want to test. The selected recipe’s preview page opens. If the recipe is active, click Stop.
Then, select Test recipe from the Start recipe dropdown.
Or, click the ellipsis icon next to a recipe on the Recipes page, and click Edit. The selected recipe page opens.
Click Test recipe.
Customize recipe
Each recipe has the following components: Trigger, Actions, and Conditions. You can customize any recipe depending on your specific requirements.
Let’s take a default recipe as an example to customize it further.
Default recipe: xMatters Incident (create/update) to Freshservice Service Request (create/update)
You can click any component, and use the Edit option associated with the component to customize. For example, the Trigger component (as shown in the following figure).
Trigger
This recipe component acts as the starting point for any recipe. For this default recipe, the trigger is fetching a new or updated incident from xMatters and syncing it with a Freshservice service request.
You can customize the trigger in the following ways:
View the list of optional fields available for a particular trigger.
Modify optional fields for existing triggers or add trigger conditions.
Add multiple trigger conditions using the ‘+’ option below the trigger conditions section. You can choose to set up AND or OR conditions.
Set the trigger data by choosing from a list of available attributes.
Configure the date and time for trigger
When configuring a trigger (for example, New record in an app), you may see the When first started, this recipe should pick up events from incidents created after this date field.
This field allows you to set a start date and time, ensuring that only records created or updated after this date and time are processed.
If not specified, the default behavior is used for fetching records (for example, fetching incidents created or updated one hour ago).
Important:
Avoid processing old data, if you want only the new data from a specific time period onwards.
Backfill historical data, if you want to start processing data from a specific past date.
Prevent duplicate processing of data to ensure the recipe does not pick up outdated records.
Condition
This component acts as a checkpoint within the recipe flow and executes a specific set of actions based on the matched condition.
Here, the recipe checks if a new incident is created or an existing incident is updated in xMatters. Accordingly, a service request is created or updated in Freshservice.
You can check and edit the data fields and conditions.
Action
The recipe performs a specific set of actions based on the conditions met. For example, the recipe creates or updates a service request in Freshservice for a new or existing incident in xMatters.
You can customize the following parts of the action:
Perform any action from the existing set of available actions.
Map values to the corresponding fields in Freshservice.
Add more fields from the available set of optional fields.
After customizing a recipe, you can save or test it to ensure it's working correctly.
Check failed recipe or jobs
To view and troubleshoot failed jobs under a recipe, follow these steps:
Click Preview next to a specific recipe on the Recipes page.
Go to Jobs.
View a list of all the jobs executed under a particular recipe.
Filter the failed jobs using the All statuses filter.
Click a failed job to view the error details and identify the cause of failure.
Resubmit the job after your review to fix the issue.
Configure widget settings
After you activate recipes as per your requirement, you can configure widget settings.
Go to Admin > Automation & Productivity > Extensibility > Connector Apps.
Click xMatters Connector App. The Overview page opens.
Click Widget Settings. This page shows you a list of fields you can select to display in the xMatters widget on any ticket details page across different workspaces.
Enable the xMatters widget toggle.
Select the fields you want to display in the xMatters widget on the ticket details page.
Note: A sample illustration is shown on the right-side section for your reference.
Click Save.
The widget will now be active and available to use within Freshservice tickets (as shown in the following figure).
Link tickets with xMatters widget
You can link any Freshservice ticket using the xMatters widget from the ticket details page across different workspaces.
Go to Tickets > List.
Click any ticket Subject to go to the ticket details page.
Click Link this ticket in the xMatters Connector App widget (as shown in the following figure).
Fix linking-ticket error
When there is any recipe error, the Link this ticket option will not be available. You can fix this issue by updating the recipe.
Go to Tickets > List.
Click any ticket Subject to go to the ticket details page.
Use the Click here to fix it link in the xMatters Connector App widget (as shown in the following figure).
Note: You will be redirected to the xMatters Connector App Overview page.
View merged ticket notes
When two or more timeline notes are added to an xMatters incident in a specific time frame, those notes are merged and shown under the Conversations section of the associated Freshservice ticket (as shown in the following figure).
Note: The sync between xMatters incident timeline notes and Freshservice ticket notes is initiated only when an xMatters incident is updated. Therefore, xMatters to Freshservice notes sync is based on the xMatters incident update intervals.
Note: For information on frequently asked questions (FAQs) related to the Connector Apps in Freshservice, see Connector Apps: Frequently Asked Questions (FAQs).