Zapier integration

The more online applications your company use, the more is the need to automate tasks between them. Starting with version 8.5, you can use Zapier to connect Alloy Navigator with other apps to automate repetitive tasks and have more time for actual work. This article describes how to do it.

About Zapier

Zapier is an online automation tool that helps connect web apps without coding or relying on developers to build the integration.

In Zapier, automated tasks between applications are called Zaps. A Zap consists of a trigger event and an action. An event in one app is used as a trigger to perform a corresponding action in another app. For example, since we talk about Alloy Navigator, you can use Zapier to automatically send a message to your Support Team channel in Slack when a new Incident is submitted in Alloy Navigator — that would be a Zap.

A single Zap can chain multiple actions in various apps together. For example, a single Zap can capture a message in a Slack channel, create an Incident, and post the Incident number back to the message sender in the Slack channel.

Supported objects, triggers, and actions

Currently, the following Alloy Navigator objects can be used in Zapier integrations:

• Incidents
• Change Requests
• Persons

Various events in Alloy Navigator can become triggers for your Zapier integrations.

Trigger	Triggers when
New Change Request	A new Change Request is created.
New Change Request activity	A new Activity is added to any Change Request.
Change Request status change	A Status of a Change Request is changed.
New Incident	An Incidentis created.
New Incident activity	A new Activity is added to any Incident.
Incident status change	A Status of an Incident is changed.

Actions either create something in Alloy Navigator or search for something in Alloy Navigator.

Action	What the action does
Create Incident	Creates a new Incident in Alloy Navigator.
Lookup Incident	Retrieves an Incident record by ID or OID.
Search Person	Searches Person by primary email address.
Lookup Change Request	Retrieves Change Request record by ID or OID.
Lookup Person	Retrieves Person record by ID or OID.

Before you begin

To allow Zapier to connect to Alloy Navigator, these things are required:

• Zapier account

  To integrate your Alloy Navigator with other apps, you will need a Zapier account at https://zapier.com/. If you do not have a Zapier account, sign up.

• Alloy Navigator account for integration

  Zapier will ask you for the username and password of an Alloy Navigator account. We recommend that you use a dedicated technician account with Standard or Windows authentication. This account must have permissions for the actions your integration will perform in Alloy Navigator.

  INFO: For details, see Administration Guide: Creating and Maintaining Technician Accounts.

• Alloy Navigator API endpoint URL

  Zapier will ask you for the URL of Alloy Navigator API's endpoint, for example:

  https://mycompany.com/alloynavigator/api

  Before you start creating a Zap, make sure that Alloy Navigator API module is installed and configured for the Access Token user authentication.

  INFO: For instructions, see Installation Guide: Installing and Configuring the API Module.

Creating zaps

To get started, check out our ready-to-use Zaps for common automation tasks. If you find what you are looking for, click Connect these Apps and follow the on-line instructions that will walk you through the process.

For example:

• Send a Message to a Slack channel when an Incident is submitted in Alloy Navigator

• Submit an Incident when a CloudWatch Alarm state changes

• Create a Trello card when a Change Request is approved

• Convert Messages in Microsoft Teams into Incidents in Alloy Navigator

NOTE: Contact our Support Team, and we will help you to set up the integration and let Alloy Navigator and Zapier automate your workload.