Delete Ticket

This Snap has exactly one document input view.

Each input document identifies one ticket to delete. Reference the ticket ID in Ticket ID using the $ notation.

• Mapper

This Snap has at most one document output view.

With a Batch size of 1, each output document contains the ticket's id and success set to true. Otherwise, each output document is the background job's result for one ticket, including its id, status, and success.

• Mapper

Label*

Specify a unique name for the Snap. Modify this to be more appropriate, especially if more than one of the same Snaps is in the pipeline.

Default value: Delete Ticket

Example: Delete spam tickets

Enter the numeric Zendesk ID of the ticket to delete.

Default value: None

Example: $id

Enter the number of ticket IDs to accumulate before sending a single delete request, from 1 through 100. With 1, the Snap deletes each ticket with its own request. With a larger value, the Snap deletes each batch with one request, which Zendesk processes as a background job.

Default value: 1

Example: 50

When selected, the Snap first deletes each ticket, then permanently purges it from the deleted tickets queue. Purged tickets cannot be recovered.

Default value: Not selected

Example: Selected

Enter the number of times the Snap should retry the API call on connection errors or 5xx responses. On a 429 response, the Snap automatically retries after the interval specified in the server's Retry-After header, overriding the Retry interval value. On a 401 response, the Snap reloads the account credentials and retries before counting the attempt against this limit.

Default value: 5

Example: 3

Enter the number of seconds to wait between retry attempts. The Snap also waits this long between checks on a background job's status, and checks up to 100 times.

Default value: 3

Example: 5

Snap execution

Default value: Execute only

Example: Validate & execute