Scriptera
Exolve and Zammad automations
Ready-made scenarios where Exolve and Zammad work for you: pick one — a copy appears in your account and runs on its own.
27 scenarios
- New messages in Exolve — Updating users in Zammad
- New groups in Zammad — Running apis in Exolve
- New groups in Zammad — Sending messages in Exolve
- New messages in Exolve — Users in Zammad
- New messages in Exolve — Deleting users in Zammad
- New users in Zammad — Running apis in Exolve
- New users in Zammad — Sending messages in Exolve
- New tickets in Zammad — Sending messages in Exolve
- New messages in Exolve — Tickets in Zammad
- New messages in Exolve — Companies in Zammad
- Updated tickets in Zammad — Sending messages in Exolve
- New companies in Zammad — Sending messages in Exolve
- New messages in Exolve — Tickets in Zammad — variant 3
- Emails from mailgun — as tickets in Zammad and an alert in Exolve
- Urgent messages from Telegram — into Telegram and Zammad
- Unassigned support tickets — as a list in exolve
- Early churn-risk detection from Zammad tickets
- Hiring spikes at your accounts — straight to team chat
- A support ticket digest — every morning
- A daily access check: two-factor and stale keys
- Morning briefs for your meetings — who and where from
- Enrich leads and get alerts on strong ones
- A summary of support tickets — topics and customer mood
- Support metrics from two systems — in one weekly report
- SLA monitoring that warns before a ticket breaches
- Payment issue handling: a reply to the customer, an escalation to the team
- Response to a leaked access key — deactivate and lock down
