For each event, if a story was added in regards to “section_changed” continue with the code. I found a post by a leader explaining what stories are. In the users eyes they are basically those comments that identify changes to the task.
I will continue to try and find a good way to approach this, but any input is welcome.
From the code snippet in your post, I assume you’re wanting to do this programmatically using the API, not in the UI using rules? (If so, I want to move your post to the API forum section.)
If you can store values on your end, then record the section for the tasks within the project. Then use a project-level webhook to capture changes on those tasks; when you get a change event, read the task, check its current section against the value in your data store to determine if it’s changed.
Use the story-based approach you outlined. If you use this approach, just be cognizant of story consolidation which means you aren’t guaranteed to get every single change on a task.