PSA Integration

AutoTask Integration Documentation

Credentials Requirements:

• Username:
  This can be the email ID associated with the AutoTask user account.

• Password:
  The password for the AutoTask user.

• Tracking Identifier / API Integration Code:
  Required for managing tickets via the API.

Custom Settings:

• QueueId:
  Specifies the queue category for ticket assignment within AutoTask.

• CompanyId:
  Necessary for associating the ticket with the correct company during the ticket creation process in AutoTask.

For the credentials you need to create an API user

Got to Admin-> Company Settings & Users
 

• Select Resources/Users -> Resources/Users

• Select New drop down -> New API User

• Enter the details and press Generate Key(Username) and Generate Secret (Password). The Press Custom (Internal Integration) and give a name, You will get the Tracking Identifier also. Please Save and Close. If not saved it will not Work.

Jira Integration Documentation

Credentials Requirements:

• API URL Name:
  The domain name for your Jira instance (e.g., "roboshadow" for https://roboshadow.atlassian.net/).

• Username:
  The email address associated with your Jira account. User Should have access to manage ticket in the Project.

• API Token:
  The token generated for API access.

• Project Key:
  The key of the Jira project where issues will be created.

Custom Settings:

• IssueType:
  Specifies the type of issue to be created in Jira.(For Eg: Task, Service Request etc..)

SuperOps Integration Documentation

Credentials Requirements:

• API URL:
  The base URL for the SuperOps API (e.g., " https://api.superops.ai/msp" or for Europe, " https://euapi.superops.ai/msp"). Change to the other if the one not worked.

• Customer Subdomain:
  The unique subdomain for your organization (e.g., "roboshadow" for https://roboshadow.superops.ai/).

• Bearer Token:
  The token for API authentication.

Custom Settings:

• Client AccountId:
  The ID of the client account in SuperOps.

• UserId:
  The ID of the user within the SuperOps system.

Note:

SuperOps integration will not work if IP restriction is enabled in your SuperOps account, as the API access is also restricted by IP. Please disable the IP restriction if there.

Zendesk Integration Documentation

Credentials Requirements:

• API URL Name:
  The domain name for your Zendesk.(e.g., "https://{domain}.zendesk.com/api/v2/tickets").

• Username:
  The email address associated with your Zendesk account.

• Password:
  The password for the Zendesk account.

ServiceNow Integration Documentation

Credentials Requirements:

• API URL Name:
  The instance ID for your ServiceNow environment (e.g., "dev215629" for https://dev240799.service-now.com ).

• Username:
  The username for your ServiceNow account (e.g., "admin").

• Password:
  The password for your ServiceNow account.

FreshService Integration Documentation

Credentials Requirements:

• Domain:
  The subdomain for your FreshService account (e.g., "roboshadow" for https://roboshadow.freshservice.com/).

• Requester Email:
  The email address of the requester (e.g., "paul.johnson@roboshadow.com").

• API Key:
  The API key for authentication.

Syncro Integration Documentation

Credentials Requirements:

• SubDomain:
  The subdomain for your Syncro account (e.g., "roboshadow" for https://roboshadow.syncromsp.com/).

• API Key:
  The API key for authentication.

Custom Settings:

• CustomerId:
  Represents the business name.

SYNCRO API permissions

·         Customers – List/Search

·         Select All Tickets

Halo Integration Documentation

Credentials Requirements:

• Domain:
  The domain for your Halo account (e.g., "roboshadow").

• Client ID:
  The unique client ID for authentication.

• Client Secret:
  The client secret key for secure access.

Custom Settings:

• Category:
  Specifies the category for ticket creation (e.g., "IT Security Threats > Software Vulnerability").

   

For Authorization:

For authorization, we use the client_credentials method with the Client ID and Secret.
Create a new application in the page: https://{domain}.halopsa.com/config/integrations/api/applications.
Ensure permissions are set to read:tickets and edit:tickets read:customers. You can create a client at:

Go to the page and click New

In the Details select Client ID and Secret (Services)
Press Generate
You will now get ClientId and Secret

In the Permissions Tab enable read:tickets, edit:tickets, read:customers
 

Atera Integration Documentation

Credentials Requirements:

• apiKey:
  apiKey for the Account

Custom Settings:

• EndUser:
  Represents the EndUser.

For Api Key:

Go to Admin then select API