- 16 Mar 2023
- 3 Minutes to read
Zendesk - Create Ticket
- Updated on 16 Mar 2023
- 3 Minutes to read
Zendesk - Create 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).
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
- Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapter Fetch History and Asset Investigation Modules
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
- Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
- 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.
These fields must be configured to run the Enforcement Set.
Click to view Required Fields
- Zendesk domain (required) - Provide credentials to connect Zendesk: domain, user email and password.
- User Name Email (required) - Enter the email address for the user account.
- Password (required) - Input the API key.
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.
These fields are optional
Click to view Additional Fields
Verify SSL - 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, 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.
Ticket subject (required) - Provide the ticket subject.
Ticket body (required) - Provide the ticket body.
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.
_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_
Priority (required, default: Normal) - Select the ticket priority: Low, Normal, High, Urgent.
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.
Attach a CSV file with the affected entities - Attach a CSV file containing the results of the query.
For more details about other Enforcement Actions available, see Action Library.