Webhook sending Extra API calls.

I’m currently trying to set up a Webhook that fires when a task is added to a specific project. This is the current Webhook I have set up.

{
    "data": {
        "gid": "************7713",
        "resource_type": "webhook",
        "resource": {
            "gid": "************6918",
            "resource_type": "project",
            "name": "************[PROGRAM] WEBPROD ************************"
        },
        "target": "************************************.trayapp.io",
        "active": true,
        "created_at": "2021-11-17T22:50:22.649Z",
        "last_failure_at": null,
        "last_failure_content": "",
        "last_success_at": "2021-11-17T22:50:23.720Z",
        "filters": [
            {
                "resource_type": "task",
                "resource_subtype": null,
                "action": "added",
                "fields": null
            }
        ]
    }
}

The issue is, after a task is added to that project, then a rule fires to send that task to another project, the Webhook fires 5 more times.
image

Those additional Webhook triggers are NOT firing on the specified Webhook filters or the project that was specified. Here is an example Event:

{
				"user": null,
				"created_at": "2021-11-17T22:18:54.539Z",
				"action": "added",
				"resource": {
					"gid": "************5584",
					"resource_type": "story",
					"resource_subtype": "added_to_project"
				},
				"parent": {
					"gid": "************0439",
					"resource_type": "task",
					"resource_subtype": "default_task"
				}
			}

The workaround I am currently using that has me unblocked is I duplicated the project that the rule was pushing the task to, changed the rule to push the task to that duplicated project, and now it is only sending one API call.

I believe this is a bug? I am not exactly sure if I am misunderstanding how the system decides to send a Webhook or if this is a bug.

Can anyone shed some light on this situation?
Thank you

Maybe @Phil_Seeman can help. From what I remember he said, there is a lot of noise with webhooks and you might have to discard some of those events.

1 Like

Yes, you can expect to get multiple webhooks for a task change. For example, you can get a “task change” event, then one or more “story” events which log the task change that just occurred.