Most of the process involved in integrating Guardz with SuperOps takes place in the Guardz platform.
Before you begin the integration, make sure:
That you have an active, paid Guardz subscription
That you have a technician role with permissions to add custom fields enabled
You’ll need two things from SuperOps to integrate your portal with Guardz:
API token
Subdomain name
If you haven’t created a technician role yet, here’s how:
Creating a technician role
1. Go to `Settings` > `Roles and Groups` > `Technician Roles`.
2. Click on `Create` at the top right corner.
3. Enter the role name and description.
4. Configure the role as follows:
1. MSP Settings:
- Technicians - `View` only
- Technician Groups - `View` only
2. Ticketing Settings:
- Ticket Fields - `View` only
- SLA Policy - `View` only
- Reply Template - `View` only
- Ticket Form - `View` only
- Runbook - `View` only
3. Client Settings:
- Client - `View` only
- Custom Fields - `Add` & `View`
- All Clients - `Allow`
4. Ticketing:
- Tickets - All permissions
- All Tickets - `Allow`
- Set SLA - `Allow`
- Views - `View` only
5. Task Settings:
- Task Template - `View` only
5. Click on `Save` at the top right corner to create the role.
Create a technician or assign the role to an existing technician
1. Go to `Settings` > `My MSP` > `Technicians`.
2. Create a new technician by clicking the `Create` button at the top right corner, or edit an existing technician.
3. Under the `Role` field, select the role created in the previous step.
Get the Subdomain name and API token of your SuperOps account
1. Login as an admin to your SuperOps account.
2. Go to `Settings` > Marketplace > Guardz. On this page, you’ll find instructions to help you configure the integration.
3. Copy the text under `The subdomain's name`, **without** the `https:\\` or `.superops.ai` part.
4. Save it for later when configuring the integration in Guardz.
5. You’ll find the API token right next to the subdomain. Click the Copy icon to copy the API token. Ensure that you’re logged in as a technician with the role created earlier.
4. Copy the token and save it for later when configuring the integration in Guardz.
Setting up the Integration in Guardz
1. Log in to your admin account in Guardz application, click on your user icon at the bottom-left, and select PSA Integration
2. Select `SuperOps` in the integrations list
3. Use the Subdomain name and API token you saved earlier to fill in the required fields.
4. Follow the other steps to create the integration, once it's done and active you should start seeing issues from Guardz as tickets in SuperOps (according to how you configured the integration)
Updating Tickets in SuperOps
When integrating SuperOps with Guardz, you can configure tickets in SuperOps to update automatically whenever their status changes in Guardz. However, if SuperOps requires mandatory fields to be filled when closing a ticket, this can prevent Guardz from updating the ticket status to "closed."
To enable Guardz to successfully update and close tickets in SuperOps, you can set up event automations within SuperOps. Follow the steps below:
Setting up Event Triggers
Navigate to Setting > Event Triggers > Create New Event Triggers
2. Give your event trigger a Name and Description
(For example: “Guardz Integration - Close Tickets”)
3. Choose Ticket Creation
4. Under Conditions > Choose “Source” > “is” > “Integration”
5. Choose "Subsource" > "is" > "Guardz "
6. Under perform action, Under Set property -> Choose from the list . (Choose the one which was configured as mandatory
(Please note: Select one or more mandatory properties that are required to update the ticket. If not entered correctly, tickets may fail to close as expected.)
With this automation in place, whenever a ticket is created from Guardz, the required fields are automatically populated in the ticket's detail page within SuperOps. This setup allows Guardz to programmatically update and close tickets based on issue status changes, without any dependencies or manual intervention from technicians. As a result, tickets will be seamlessly closed through Guardz without encountering issues related to mandatory fields.