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
- Navigate to Automations > Integrations.
- Search for Naverisk.
- 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.
- 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 Name | Description | Required |
|---|---|---|
| Client ID | Jinja 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 Name | Description | Required |
|---|---|---|
| Client ID | Jinja templated client ID. Example: {{parent_table_client_id}} | Required |
| Device ID | Jinja 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 Name | Description | Required |
|---|---|---|
| Include States | Jinja-templated command separated ticket states. Possible Values: [Active, Assigned, Closed, Archived, AutoClosed]. Example: Active, Assigned | Required |
| Limit | Limit number of tickets. Default is 10. | Required |
| Monitor List | Represents the list of monitors. Default is (False). | Required |
| Console Type | Represents the console type of returned tickets. Default is All. | Required |
| SLA Class ID Filter | Jinja-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 Filter | Jinja-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 Column | Select sorting column. Default is (LastAlert). | Required |
| Sort Direction | Select 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 Name | Description | Required |
|---|---|---|
| Incident ID | Jinja-templated incident ID. Example: {{parent_table_incident_id_column}} | Required |
| Client ID | Jinja-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 Name | Description | Required |
|---|---|---|
| Client ID | Jinja-templated client ID. Example: {{parent_table_client_id}} | Required |
| Trigger | Jinja-templated trigger. Example: {{parent_table_trigger}} | Required |
| Description | Jinja-templateddescription.Example: {{parent_table_description}}. | Required |
| Trigger Type | Jinja-templated trigger type.Possible values:[Once, Daily, Weekly, Monthly] Example: {{parent_table_trigger_type} | Required |
| Ticket Incident State ID | Jinja-templated ticket incident state id. Possible values:[Unassigned, Assigned, Close, Archived] Example:{{parent_table_state_id}} | Required |
| Ticket Type | Jinja-templated ticket type. Possible values: [Incident, Problem, ServiceCell, Change, Project] Example: {{parent_table_ticket_type}}. | Required |
| Device ID | Jinja-templated device ID. Example: {{parent_table_device_id_column}}. | Required |
| SlaClass ID | Jinja-templated SlaClass ID. Possible values: [Performance, Availability, Security, Backup, Support, Antivirus, Sales]. Example: {{parent_table_sla_class_id}}. | Required |
| SlaStatus ID | Jinja-templated SlaStatus ID. Possible values: [Warning, Threat, Failure, Information]. Example: {{parent_table_sla_status_id}}. | Required |
| Ticket Category ID | Jinja-templated ticket category ID. | Required |
| User ID | Jinja-templated user ID. | Required |
| Ticket Source ID | Jinja-templated ticket source ID. | Required |
| Ticket Job Type ID | Jinja-templated ticket job type ID. | Required |
| Ticket Status ID | Jinja-templated ticket status ID. | Required |
| Trigger Once Date Time | Jinja-templated trigger once date time. Example: 2021-05-27 08:59:00 | Required |
| Trigger Daily Recurs Every | Jinja-templated trigger daily recurs every. Example: 1 | Required |
| Trigger Daily Occurs Time | Jinja-templated trigger daily occurs time.Example: 14:44 | Required |
| Trigger Daily Start Date | Jinja-templated trigger daily start date. Example : 2021-05-26 | Required |
| Trigger Daily End Date | Jinja-templated trigger daily end date. Example: 2021-05-26 | Required |
| Trigger Weekly Recurs Every | Jinja-templated trigger weekly recurs every. Example: 1 | Required |
| Trigger Weekly Week Day | Jinja-templated trigger weekly week day. Example: 1 | Required |
| Trigger Weekly Occurs Time | Jinja-templated trigger weekly occurs time. Example: 15:36 | Required |
| Trigger Weekly Start Date | Jinja-templated trigger weekly start date. Example: 2021-05-26 | Required |
| Trigger Weekly End Date | Jinja-templated trigger weekly end date. Example: 2021-05-26 | Required |
| Trigger Monthly Recurs Every Day | Jinja templated trigger monthly recurs every day. Example: 1 | Required |
| Trigger Monthly Recurs Every Month | Jinja-templated trigger monthly recurs every month. Example: 1 | Required |
| Trigger Monthly Occurs Time | Jinja-templated trigger monthly occurs time. Example: 15:23 | Required |
| Trigger Monthly Start Date | Jinja-templated trigger monthly start date. Example: 2021-05-26 | Required |
| Trigger Monthly End Date | Jinja-templated trigger monthly end date. Example: 2021-05-26 | Required |
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 Name | Description | Required |
|---|---|---|
| Client ID | Jinja-templated client ID. Example: {{parent_table_client_id}} | Required |
| Device ID List | Jinja-templated device ID list. | Required |
| Trigger | Jinja-templated trigger. | Required |
| Description | Jinja-templated description. | Required |
| Ticket Job Type ID | Jinja-templated ticket job type ID. | Required |
| SlaClass ID | Jinja-templated SlaClass ID. Possible values: [Performance, Availability, Security, Backup, Support, Antivirus, Sales]. Example: {{parent_table_sla_class_id}}. | Required |
| SlaStatus ID | Jinja-templated SlaStatus ID. Possible values: [Warning, Threat, Failure, Information]. Example: {{parent_table_sla_status_id}}. | Required |
| User ID | Jinja-templated user ID. | Required |
| Ticket Source ID | Jinja-templated ticket source ID. | Required |
| Ticket Category ID | Jinja-templated ticket category ID. | Required |
| Ticket Status ID | Jinja-templated ticket status ID. | Required |
Output
A JSON object containing the following items:
Updated about 1 year ago