The Future Tickets app allows advanced creating/updating of follow-up tickets via a Webhook which the app automatically creates for you named App - Future Tickets - Create or update.
The webhook accepts the following parameters:
| Parameter | Value |
| name* | What label to give the future ticket that is about to be created. If a future ticket already exists with that name, that one will be updated instead. |
| date* | The value of a ticket field of type "Date". |
| time* | The value of a ticket field of type "Text" or "Regex". These field accepts many ways to express time, such as "1pm", "13:00", "1:00 PM". A regex field has the added benefit of validation. |
| timezone | An IANA timezone value such as "Australia/Melbourne" or "America/Los_Angeles". You can also use the placeholder {{current_user.time_zone}} for a dynamic timezone based on the user who triggers the webhook. |
| ticket_template_id* | The ID of a valid Ticket template defined within the Future Tickets app that should be used when the follow-up ticket is created. |
| minutes_from_now | Instead of specifying "date", "time" and "timezone", have the future ticket set for a specified time period from now. |
| hours_from_now | |
| days_from_now |
*Mandatory field.
Note that date, time and timezone are mandatory unless a *_from_now parameter is specified.
Your workflow ID can be found at the bottom of the page of the particular workflow settings in the app.
Below are some examples for how to configure the webhook on a trigger.
Example of a future ticket automatically created for a period after some ticket conditions were met:
Example of a future ticket automatically created based from ticket fields: