TicketWave v1.0.6 - Patch Notes

In this release, we introduced webhooks so your own applications can react to ticket events, added our new Ticket Automation module, launched the /feedback command and made parts of your dashboard update in realtime.

TicketWave Bot

🔗 Webhooks - TicketWave in your own application

Log channels write an embed into Discord for humans to read. Webhooks hand the raw event to your code. Whenever something happens in your server, TicketWave sends a signed POST request to a URL you own - so you can push ticket events into your own app, your CRM, your database or into a Zapier, n8n or Make automation. Please see more at our docs entry

• We added six event types you can subscribe an endpoint to: ticket.created, ticket.closed, ticket.updated, message.sent, blacklist.added and blacklist.removed. Please see more at our docs entry
• We sign every request with a HMAC-SHA256 signature over the timestamp and the body, so your receiver can verify that a request really came from us and a captured request cannot be replayed later.
• We retry a failed delivery up to three times with a growing delay, so a short hiccup on your side does not cost you an event.
• We only accept https:// endpoints and check the target host before every single delivery, so an endpoint can never be pointed at an internal address.
• Every server can create up to 5 endpoints, each with its own signing secret and its own list of event types.
• Webhooks are a premium feature.

🤖 Ticket Automation

Our new Ticket Automation module handles the moments your team should not have to think about. You pick a trigger, you pick what happens - and TicketWave does the rest.

• We added the Member Leaves the Server action. Open tickets of a member who left can now be closed automatically, in realtime and with a nightly fallback check in case the bot was offline while the member left.
• We added the Member Rejoins the Server action. A leave resets the channel permissions of a member, so a returning member would no longer see their own open ticket. With this action their access is restored automatically and the ticket channel is informed that the owner is back.
• We added the Ticket Without a Reply action. If a ticket stays unanswered by your team for longer than the delay you configured, your staff gets a reminder via DM - including the ticket details and a jump button. A claimed ticket only reminds the staff member who claimed it, and there is only one reminder per unanswered period, so nobody gets spammed. This action is a premium feature.
• We added an on and off switch for the whole module, so you can pause every automation at once without losing your configuration.

📮 New /feedback command

We would like to know what you think, so we added a short and completely optional feedback flow to the bot. /feedback asks whether you are staff or the owner of the server, how happy you are with the setup and the customization, whether you are missing any commands and gives you a free text field for everything else. It takes less than a minute and it lands directly with our team.

General

• We added optional subcategories. Exactly like optional ticket steps, the subcategory selection of a category can now be marked as optional, so your members can skip it with a skip button.
• We added the option to gift premium to a server, for example as the prize of a giveaway. Gifted premium behaves exactly like a paid plan and is shown as its own type in your profile and on your premium page.
• We added discordbotlist.com as an additional bot list you can vote on, so your Vote Coins and your streak now grow on both lists.
• We fixed a security issue in the ticket feedback, where a rating could be submitted by someone who was not the owner of the ticket and with an invalid star count.
• We fixed an issue where a feedback channel that does not belong to your server could be saved. The channel is now validated before it is stored.
• We improved the error message you get when your feedback channel is invalid.
• We fixed an issue where the bot could miss its own startup event.
• We added an internal telemetry endpoint, so we notice authorization problems with our application much faster.

TicketWave Website

• We added a complete Webhooks section to your dashboard. You can create, edit, disable and delete endpoints, reveal or regenerate their signing secret and choose exactly which events an endpoint receives.
• We added a delivery history for your webhooks. Every delivery shows the event type, the status, the response code, the duration and how many attempts were needed - including the full request and response payload. Deliveries are kept for 30 days.
• We added a Send test event button, so you can verify your receiver with a real, fully signed request before a live ticket depends on it, and a retry button to send any delivery again.
• We added the new Ticket Automation module to your settings, with a new action based layout: you pick what happens on a trigger, and the settings that belong to the selected action appear right underneath it.
• We added the optional subcategory switch to the ticket category creator.
• We added a bulk setup for your log channels. You can now pick one channel and apply it to every log type at once, see which types are already configured and where they would be moved from - or remove all entries in one step.
• We made your blacklist realtime. A blacklist added or lifted through the bot now appears in your dashboard instantly, without a reload and without polling.
• We updated our premium comparison table with everything that arrived over the last releases, including webhooks, additional ticket access, the ticket list, the instant close and the ticket reminder cooldown.
• We added the gifted premium to your profile and to your premium page.
• We updated the translations for all supported languages on the website.

TicketWave Docs

We added a completely new Developer section to our documentation, available in every supported language:

• Developers - what this section is for and when you should use webhooks instead of log channels: Overview
• Webhooks - how to create an endpoint, the endpoint requirements, the headers, the signature and the retry behaviour: Overview
• Event Reference - every event type with its exact payload: Events
• Example Server - a complete, runnable Express receiver that verifies signatures, protects against replays and deduplicates retries: Server Example

We also added the new section to our start page and to our sidebar.

---

We are committed to continuously improving our product and providing you with the best experience possible. If you have any questions or feedback, please don't hesitate to reach out to us on our Discord server.

Thank you to everyone. Your feedback makes TicketWave better and stronger than ever.