I one case a parent of a task is a project, in other - section. It makes no difference how I setup a webhook filtering. The result is always the same. Any ideas what can cause event duplicating?
Hey @mantisana, What you’re seeing is actually expected behavior with Asana’s webhooks. When a new task is created, Asana fires separate events for each “parent” relationship that gets established — one for the task being added to the project, and another for the task being added to a section within that project.
That’s why your payloads differ slightly: in one, the parent is the project; in the other, it’s the section. Even with webhook filters, Asana will still send both because they’re technically distinct events in the data model.
If you want to avoid processing the same task twice, you’ll need to deduplicate on your side — e.g., track the task GID + action + a short time window (a few seconds) and skip duplicates.
This isn’t something you can stop at the webhook source, unfortunately — it’s just how Asana structures creation events.
Thanks for your clarification. I can use filtering by a parent type right after a webhook module to achieve my goal.
Great to hear this @mantisana!
