Update Ticket

This Snap has exactly one document input view.

Each input document carries the ticket changes at the location that Data path points to. The Snap provides a ticket input schema, so you can map the ticket fields in an upstream Mapper Snap.

• Mapper

This Snap has at most one document output view.

With a Batch size of 1, each output document is the ticket as Zendesk updated it. Otherwise, each output document is the background job's result for one ticket.

• 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: Update Ticket

Example: Close resolved tickets

Enter the numeric Zendesk ID of the ticket to update. When you select Apply same data to multiple tickets, enter a comma-separated list of ticket IDs instead.

Default value: None

Example: $ticketId, or 101,102,103 when Apply same data to multiple tickets is selected

When selected, Ticket ID accepts a comma-separated list of IDs, and the Snap applies the same changes from Data path to every listed ticket in a single request. The Batch size field is hidden.

Default value: Not selected

Example: Selected

Enter the path in the input document that resolves to the ticket object with the changes to send to Zendesk. The value must be a single object, not an array. Enter $ to use the entire input document.

Default value: $ticket

Example: $changes

Appears when Apply same data to multiple tickets is not selected.

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

Default value: 1

Example: 50

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