Automation trigger when adding tag

Hi @kl-edwin 

Hope you are well.

Thank you for reaching out about this, Right now we do not have this as an option in Event Node. We are bringing something very similar in the future. We have this on our Roadmap. So when a Tag is added/updated, It would act as a triggering point for the Workflow.

Thanks and Regards,

Amy

​@Ammar KB is this still in the works? It would be useful to use “tag added” as an event.

Would really like to have this, is Freshworks still working on this?

Sure! Since One Express Cargo specializes in logistics, freight forwarding, and cargo solutions, you could relate the automation trigger to improving shipment tracking, order management, or customer notifications.

Here’s a possible response:

"Automation trigger when adding tag"

If you're looking to automate processes when a tag is added, this can be highly useful in logistics and freight forwarding. At One Express Cargo, we leverage automation to enhance our operations—for example:

✅ Real-time Shipment Updates – When a tracking tag (e.g., "In Transit," "Customs Cleared") is added, customers receive instant notifications.
✅ Order Prioritization – Automatically flag high-priority shipments (e.g., "Urgent" or "Fragile") for faster processing.
✅ Customer Follow-Ups – When a tag like "Pending Documentation" is added, an automated email reminds clients to submit required paperwork.

Automation helps streamline operations and improve customer satisfaction. How are you planning to use it in your system? 🚀

Would you like any modifications to match your company's exact use case? 😊

Hi as of now you cannot fire an automation (or have an Event Node trigger) simply by adding a tag to a ticket. The “Ticket is modified” trigger doesn’t fire when a tag is added. For now, if you need to trigger an automation based on changes to a ticket, you’d have to rely on other ticket update events until they add a dedicated “tag added/updated” event trigger.
Hope it helps!

Thanks @tatereal that’s what I am currently doing but for feedback purposes I want to explain why that’s not good enough.

I have an automation that reacts to status changed from ‘any’ to ‘closed’ or ‘resolved’. If the special tag is present, a new ticket is created in another workspace. The problem here is sometimes people will add the tag after the status has already changed. Thus creating manual work. This is why adding a trigger on the tag would be huge, and also more ‘timely’.