Contents x
    Zendesk - Create Ticket Per Entity
    • 22 Sep 2024
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Zendesk - Create Ticket Per Entity

    • Updated on 22 Sep 2024
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

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

    See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

    Note:

    General Settings

    • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
    • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

    • Use stored credentials from Zendesk adapter - Select this option to use the Zendesk connected adapter credentials.
      • When you select this option, the Select Adapter Connection drop-down is available, and you can and you can choose which adapter connection to use for this Enforcement Action.

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • Select Adapter Connection - When Use stored credentials from the Zendesk Adapter is enabled, select the adapter connection the Enforcement Action will use.

    Connection Parameters

    If Use stored credentials from the Zendesk Adapter is disabled, these fields are required:

    • Sub Domain (required) - The subdomain used to access Zendesk. For example, Axonius is the subdomain for https://axonius.zendesk.com/.
    • User Name - The username of an Axonius dedicated user account.
    • Requester ID - The ID of the user creating the ticket.
    • Password - Input the API key.

    • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

    Note - ZenDesk MFA

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

    • User Name - Add the /token to the end of the account.
    • Password

    Additional Fields

    These fields are optional.

    Connection and Credentials

    When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

    • API Key/Token - An API Key/Token associated with a user account that has permissions to perform this action.
    • Password - The password of the Axonius dedicated user account.
    • 2FA Secret Key - The secret generated in Zendesk for setting up two-factor authentication for the Zendesk user created to collect SaaS Management data. See Zendesk documentation for instructions on how to set up two-factor authentication (2FA) and generate the 2FA secret.
    • Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
    • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
    • HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the  HTTPS Proxy.
    • HTTPS Proxy Password (optional) - The password to use when connecting to the server using the  HTTPS Proxy.
    • Ticket subject - Enter a short description of the ticket issue.
    • Ticket body - Enter a full description of the issue.
    • Ticket Status - Select the ticket status: new, open, pending, hold, solved, closed.
    • Assignee ID - Enter the ID of the user assigned to this ticket.
    • Group ID - Enter the ID of the group to which the user creating the ticket belongs.
    • Priority (default: Normal) - Select the ticket priority: Low, Normal, High, Urgent.
    • Create ticket even if no new entities were added - When selected, a ticket is generated even if no new assets were added to the query.
    • Tags to Add - Select or create new tags to add to the ticket.

    • Additional fields - Specify additional fields to be added as key/value pairs in a JSON format.
      For example:

      {"field1": "value1", "field2": "value2"}

      If one of the specified fields is invalid, the request might fail.

    • Gateway Name - Select the Gateway through which to connect to perform the action.

    For more details about other Enforcement Actions available, see Action Library.

    Was this article helpful?
    What's Next