Hi there! Can you clarify a bit on what you mean by updates to the “name”? Are you referring to a conversation’s subject?

I’ve run into the same challenge when working with the /events endpoint — especially around ticket name and status updates not showing up. Right now we’re handling it with a similar bulk re-pull, but like you said, it’s not very efficient and you hit the rate limits fast.

One small thing that’s helped us minimize the load is narrowing down bulk pulls by time windows using /conversations/search with tighter date ranges. It doesn’t completely solve the issue, but at least we’re not pulling everything every time.

I’d also be really interested if the Front team has plans to expose these updates as new event types. Even something lightweight like a “ticket_metadata_updated” event would make incremental syncs a lot cleaner.

Curious to hear how others are working around this in the meantime — maybe there’s a smarter approach we haven’t tried yet.

Hey all, I've got some good news. We're adding an event that triggers when the ticket status changes. For ticket name changes, however, we don't have a straightforward way to emit events without significant unplanned development work. We're hoping status change events will cover your use case—are there scenarios where names change frequently without status also changing?

If you can bear with us until next week, we should be able to start emitting the ticket status change events then. I can update this post to confirm when we go live.

Hi ​@sandboxes and ​@makoba_ngulube 
e
Front is now sending a ticket_status_update event whenever a ticket changes status. You can see a couple more details about the event in our docs.