As per Zendesk:
Automations are similar to triggers because both define conditions and actions that modify ticket properties and optionally send email notifications to customers and agents. Where they differ is that automations execute when a time event occurs after a ticket property was set or updated, rather than immediately after a ticket is created or updated.
The simpler way to think of it is automations are triggers that do not run instantly. They are time based than event based.
Instead of managing Zendesk automations via Zendesk itself, we instead use GitLab itself via the zendesk-automations project. This allows us to have version-controlled automations. For more information on managing Zendesk via the various GitLab projects, please review Using the sync repos.
| Name | Position | What it does | State |
|---|---|---|---|
| Status::Close::Close un-monitored inbox tickets | 1 | Closes tickets that were sent to an unmonitored inbox | Active |
| Status::Close::Autoclose 2FA free tickets | 2 | Closes out free 2FA tickets | Active |
| 2FA::Autoresponder::2FA Autoresponder followup | 3 | Sends a second reply to 2FA tickets 48 hours later | Inactive |
| Status::Open::Reopen standard onhold tickets after 4 days | 4 | Reopens standard on-hold tickets after 4 days | Active |
| Status::Open::Reopen namesquatting tickets after 7 days | 5 | Reopens namesquatting tickets after 7 days | Active |
| Status::Open::Reopen task tickets on due date | 6 | Reopens task tickets at their due date | Active |
| Status::Solve::Solve free tickets after 7 days pending | 7 | Moves a free ticket to solved after 7 days of being consecutively pending | Active |
| Status::Solve::Solve pending tickets after 20 days | 8 | Moves a ticket to solved after 20 days of being consecutively pending | Active |
| Status::Close::Close solved tickets after 7 days | 9 | Moves a ticket to closed after 7 days of being consecutively solved | Active |
| Ticket::Autoresponder::Reply as gitlab_support@example.com | 10 | Replies to tickets as a GitLab controlled end-user so SLA can be put back on a ticket | Active |
| Notifications::Agent::Remind agent of on-hold ticket | 11 | Sends an email about an on-hold ticket | Active |
| Notifications::Agent::Remind agent of assigned open ticket | 12 | Sends an email about an open ticket | Active |
| Notifications::Agent::Upcoming task notification | 13 | Sends an email about an upcoming task | Active |
| Notifications::Agent::Due date too far in future | 14 | Clears out the due date, reopens the ticket, and emails the agent when the due date is too far in the future | Active |
| Security::DMCA::Email vetted DMCA requests | 15 | Emails vetted DMCA requests to the security team | Active |
| Security::DMCA::Reopen on-hold DMCA requests | 16 | Reopens on-hold DMCA tickets | Active |
| SSAT::Survey::Send out survey | 17 | Sends out the SSAT survey after a ticket has been solved for one day | Active |
| Status::Close::Autoclose JiHu tickets if user is not associated | 18 | Closes JiHu tickets if there is no associated organization | Active |
| Notifications::Slack::Post soon to breach FRT tickets in spt_amer-crew | 19 | Posts soon to breach tickets in the AMER response crew channel | Active |
| Status::Close::Close unassociated partner tickets | 20 | Closes select/alliance partner tickets if there is no associated organization | Active |
