Create Zendesk Ticket
  • 12 Sep 2022
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Create Zendesk Ticket

  • Dark
    Light
  • PDF

Create Zendesk Ticket creates a ticket in Zendesk for all entities retrieved from the saved query supplied as a trigger (or from the entities selected in the asset table).

To configure Create Zendesk Ticket, from the Action Library, click Create Incident, and then click Create Zendesk Ticket.

Connection Settings

Click to view Connection Settings
  1. Zendesk domain (required) - Provide credentials to connect Zendesk: domain, user email and password.
  2. User Name Email (required) - Enter the email address for the user account.
  3. Password (required) - Input the API key.
Note - ZenDesk MFA

The ZenDesk API does not support MFA or SAML; an API token is required when using either of these:

  • User Name Email - Add the /token to the end of the account.
  • Password
  1. Verify SSL (required, default: False) - Verify the SSL certificate offered by the value supplied in Zendesk domain. For more details, see SSL Trust & CA Settings.
    • If enabled, the SSL certificate offered by the value supplied in Zendesk domain will be verified against the CA database inside of Axonius. If the SSL certificate can not be validated against the CA database inside of Axonius, the connection will fail with an error.
    • If disabled, the SSL certificate offered by the value supplied in Zendesk domain will not be verified against the CA database inside of Axonius.
  2. HTTPS proxy (optional, default: empty) - A proxy to use when connecting to the value supplied in Zendesk domain.
    • If supplied, Axonius will utilize the proxy when connecting to the value supplied in Zendesk domain.
    • If not supplied, Axonius will connect directly to the value supplied in Zendesk domain.

Action Settings

Click to view Action Settings
  1. Ticket subject (required) - Provide the ticket subject.

  2. Ticket body (required) - Provide the ticket body.

  3. Add default incident description (optional) - Includes the default incident description in the end of the ticket body. The incident description message includes the Enforcement Set name, the triggering query, the condition for executing the Enforcement, if such exists, and number of current and previous results.

    Message example:

    _Alert - "test" for the following query has been triggered: Missing Sophos_
    
    _Alert Details_
    _The alert was triggered because: The number of entities is above 0
    The number of devices returned by the query:4
    The previous number of devices was:4_
    
    _You can view the query and its results here: https://demo-   latest.axonius.com/devices?view=Missing Sophos_
    
  4. Priority (required, default: Normal) - Select the ticket priority: Low, Normal, High, Urgent.

  5. Create ticket even if no new entities were added (optional, default: True) -

    • If True, a ticket will be generated even if no new assets were added to the query.
    • If False, a ticket will not be generated if no new assets were added to the query.

To learn more about configuring Enforcement Sets, see Configuring Enforcement Sets.


First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.