Naverisk

Version: 2.0.0

Automating IT Services. Naverisk has been helping MSPs and IT Pros deliver first-class IT services.

Connect Naverisk with LogicHub

  1. Navigate to Automations > Integrations.
  2. Search for Naverisk.
  3. Click Details, then the + icon. Enter the required information in the following fields.
    • Label: Enter a connection name.
    • Reference Values: Define variables here to templatize integration connections and actions. For example, you can use https://www.{{hostname}}.com where, hostname is a variable defined in this input. For more information on how to add data, see 'Add Data' Input Type for Integrations.
    • Verify SSL: Select option to verify connecting server's SSL certificate (Default is Verify SSL Certificate).
    • Remote Agent: Run this integration using the LogicHub Remote Agent.
    • Host: Host of your Naverisk instance. Eg: https://www.mynaveriskdomain.com.
    • Username: The username used to connect to the instance.
    • Password: The password used to connect to the instance.
  4. After you've entered all the details, click Connect.

Actions for Naverisk

Get Client List

Gets the list of clients that the current user is allowed to see

Input Field

Choose a connection that you have previously created to complete the connection.

Output

A JSON object containing values of all the client names.

{
   "Keys":[
      "6",
      "8",
      "9",
      "7",
      "3",
      "1"
   ],
   "SessionGuid":"a91fb9aa-d1d9-4ee0-a1ed-4f8e7184ba8c",
   "tag":null,
   "Error":"",
   "LastRequestDateTime":"637546786107186230",
   "has_error":false,
   "error":null,
   "ClientID":1,
   "Values":[
      "test",
     "Sample"
   ],
   "Success":true
}

Get Device List

Gets the list of devices that the given client is allowed to see

Input Field

Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.

Input NameDescriptionRequired
Client IDJinja templated client ID. Example: {{parent_table_client_id}}Required

Output

A JSON object containing values of all the devices under the selected client.

Get Device Details

Gets the device details that is requested via device ID

Input Field

Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.

Input NameDescriptionRequired
Client IDJinja templated client ID. Example: {{parent_table_client_id}}Required
Device IDJinja templated device ID. Example: {{parent_table_device_id_column}}Required

Output

A JSON Object containing device details.

Get Ticket List

This operation gets the list of tickets that the current user is allowed to see.

Input Field

Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.

Input NameDescriptionRequired
Include StatesJinja-templated command separated ticket states. Possible Values: [Active, Assigned, Closed, Archived, AutoClosed]. Example: Active, AssignedRequired
LimitLimit number of tickets. Default is 10.Required
Monitor ListRepresents the list of monitors. Default is (False).Required
Console TypeRepresents the console type of returned tickets. Default is All.Required
SLA Class ID FilterJinja-templated command separated SLA class ID used to filter tickets. Available values are: [Performance, Availability, Patching, Backup, Support, Security, Scheduling, Sales]. Example: Performance, Availability. Default is to not include this filter.Required
SLA Status ID FilterJinja-templated command separated SLA status ID used to filter tickets. Available values are: [Warning, Threat, Failure, Information]. Example: Warning, Threat. Default is to not include this filter.Required
Sort ColumnSelect sorting column. Default is (LastAlert).Required
Sort DirectionSelect sorting direction. Default is (Ascending).Required

Output

An array of tickets, with each ticket in different row.

Get Ticket Histories

This operation gets the history list of the ticket

Input Field

Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.

Input NameDescriptionRequired
Incident IDJinja-templated incident ID. Example: {{parent_table_incident_id_column}}Required
Client IDJinja-templated client ID of the owner client. Example: {{parent_table_client_id_column}}Required

Output

Returns array of ticket histories, with each ticket history in different row.

Create Manual Ticket

This operation creates a manual ticket.

Input Field

Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.

Input NameDescriptionRequired
Client IDJinja-templated client ID. Example: {{parent_table_client_id}}Required
TriggerJinja-templated trigger. Example: {{parent_table_trigger}}Required
DescriptionJinja-templateddescription.Example: {{parent_table_description}}.Required
Trigger TypeJinja-templated trigger type.Possible values:[Once, Daily, Weekly, Monthly] Example: {{parent_table_trigger_type}Required
Ticket Incident State IDJinja-templated ticket incident state id. Possible values:[Unassigned, Assigned, Close, Archived] Example:{{parent_table_state_id}}Required
Ticket TypeJinja-templated ticket type. Possible values: [Incident, Problem, ServiceCell, Change, Project] Example: {{parent_table_ticket_type}}.Required
Device IDJinja-templated device ID. Example: {{parent_table_device_id_column}}.Required
SlaClass IDJinja-templated SlaClass ID. Possible values: [Performance, Availability, Security, Backup, Support, Antivirus, Sales]. Example: {{parent_table_sla_class_id}}.Required
SlaStatus IDJinja-templated SlaStatus ID. Possible values: [Warning, Threat, Failure, Information]. Example: {{parent_table_sla_status_id}}.Required
Ticket Category IDJinja-templated ticket category ID.Required
User IDJinja-templated user ID.Required
Ticket Source IDJinja-templated ticket source ID.Required
Ticket Job Type IDJinja-templated ticket job type ID.Required
Ticket Status IDJinja-templated ticket status ID.Required
Trigger Once Date TimeJinja-templated trigger once date time. Example: 2021-05-27 08:59:00Required
Trigger Daily Recurs EveryJinja-templated trigger daily recurs every. Example: 1Required
Trigger Daily Occurs TimeJinja-templated trigger daily occurs time.Example: 14:44Required
Trigger Daily Start DateJinja-templated trigger daily start date. Example : 2021-05-26Required
Trigger Daily End DateJinja-templated trigger daily end date. Example: 2021-05-26Required
Trigger Weekly Recurs EveryJinja-templated trigger weekly recurs every. Example: 1Required
Trigger Weekly Week DayJinja-templated trigger weekly week day. Example: 1Required
Trigger Weekly Occurs TimeJinja-templated trigger weekly occurs time. Example: 15:36Required
Trigger Weekly Start DateJinja-templated trigger weekly start date. Example: 2021-05-26Required
Trigger Weekly End DateJinja-templated trigger weekly end date. Example: 2021-05-26Required
Trigger Monthly Recurs Every DayJinja templated trigger monthly recurs every day. Example: 1Required
Trigger Monthly Recurs Every MonthJinja-templated trigger monthly recurs every month. Example: 1Required
Trigger Monthly Occurs TimeJinja-templated trigger monthly occurs time. Example: 15:23Required
Trigger Monthly Start DateJinja-templated trigger monthly start date. Example: 2021-05-26Required
Trigger Monthly End DateJinja-templated trigger monthly end date. Example: 2021-05-26Required

Output

JSON containing the following items:

Create Manual Ticket For devices

This operation creates a manual ticket.

Input Field

Choose a connection that you have previously created and then fill in the necessary information in the following input fields to complete the connection.

Input NameDescriptionRequired
Client IDJinja-templated client ID. Example: {{parent_table_client_id}}Required
Device ID ListJinja-templated device ID list.Required
TriggerJinja-templated trigger.Required
DescriptionJinja-templated description.Required
Ticket Job Type IDJinja-templated ticket job type ID.Required
SlaClass IDJinja-templated SlaClass ID. Possible values: [Performance, Availability, Security, Backup, Support, Antivirus, Sales]. Example: {{parent_table_sla_class_id}}.Required
SlaStatus IDJinja-templated SlaStatus ID. Possible values: [Warning, Threat, Failure, Information]. Example: {{parent_table_sla_status_id}}.Required
User IDJinja-templated user ID.Required
Ticket Source IDJinja-templated ticket source ID.Required
Ticket Category IDJinja-templated ticket category ID.Required
Ticket Status IDJinja-templated ticket status ID.Required

Output

A JSON object containing the following items:


© 2017-2021 LogicHub®. All Rights Reserved.