Zendesk Delayed Tickets Batch Action
This action is used to fetch a batch of tickets and start a flow execution for each ticket. Only tickets older than the time delay specified will be downloaded. Tickets are fetched only if they are older than the time delay and unit specified. Any tickets that already passed through this batch action will be marked with a tag to prevent duplicate executions.
Zendesk Triggers
This is a replacement of Zendesk triggers for launching flow executions. Please ensure that the Zendesk query provided is equivalent to the Zendesk triggers it replaces.
Inputs
| Name | Type | Description |
|---|---|---|
| Subdomain | String | Zendesk subdomain url |
| Username | String | Zendesk username |
| Token | String | Zendeks API token |
| Query | String | Query to filter tickets, this should replicate the conditions of a Zendesk trigger |
| Delay | String | Integer value of the time delay |
| Delay Unit | String | Unit of time, one of five. Seconds is the most granular option |
| Zendesk Tag | String | Tag to apply to tickets that have already passed through the batch action |
| Limit | String | Limit on the number of tickets that executions will be launched for. Maximum of 100 tickets can be launched at once. |
| Region | String | The region where the dashboard is accessed from. "us" for America, Asia and Australia, "eu" for Europe |
| DG API Key | String | DG API Key. Read here |
| DG API Secret | String | DG API Secret. Read here |
| Flow ID | String | ID of the flow to launch for each ticket. The flow should have inputs "id", "ticket_title", and "latest_comment" |
Outputs
| Name | Type | Description |
|---|---|---|
| Success | String | Placeholder |
Updated about 1 year ago