Trying to set up some automation through n8n with Asana. When I try to use the trigger node, I receive a 403 error. With other nodes like “Create Task”, “Delete Task”, etc., there are no problems at all, everything works fine.
Also, the most important thing to mention is that even though I have Cloudflare Zero Trust set up, I have other nodes that also work with webhooks and I don’t have any problems there at all. All other workflows are working absolutely fine.
Describe the problem/error/question
Problem running workflow
Bad request - please check your parameters
Show Details
Asana Trigger: The remote server which is intended to receive the webhook responded with an incorrect status code: 403
Asana needs to reach my n8n webhook, and Cloudflare Zero Trust is likely blocking that request. I’d make sure the webhook URL is publicly accessible and bypass authentication for that path, then recreate the trigger so Asana can validate it successfully.
Got it, thanks for confirming
I just wanted to double-check that part.
it would help to see a bit more detail to narrow this down, could you share: json, the webhook url generated by n8n and any logs when the trigger is created ?
Thanks, that helps. The test URL makes sense as an example for an inactive workflow, but it doesn’t confirm whether the Asana trigger is correctly configured in the real registration flow. What would help most here is the production webhook URL from the active workflow. I also noticed the webhook ID in the JSON does not seem to exactly match the one in the example URL, so I just want to make sure we are looking at the same trigger.
The maximum I can provide is a test webhook because I am not able to save the workflow, it just doesn’t allow me to publish it. I am sending you the trigger workflow again.
Hey @OriginalBacer, interesting that other webhooks work but Asana fails with 403. Few things to check: (1) Is your n8n webhook URL HTTPS? Asana requires HTTPS for webhook delivery. (2) Try regenerating the trigger in n8n and checking if the webhook validation succeeds. (3) Check n8n’s webhook logs — does Asana even attempt to send the webhook? If Cloudflare and firewall are open, this smells like an n8n-side webhook format issue. You could also try testing the Asana API directly with a curl request to your webhook URL from your terminal — if that works but Asana’s request doesn’t, it might be something about how Asana formats its webhook payload.
I’ve already marked the correct solution earlier in this thread, but I decided to write a detailed explanation because some of the suggestions here are simply not applicable and do not work in this specific case.
In my setup, I’m using Cloudflare Zero Trust and have it configured to bypass all traffic on a specific subdomain used for webhooks. However, when I tried to use the Asana Trigger node in n8n, it still wouldn’t work. The error looked like this:
Problem running workflow
Bad request - please check your parameters
Show Details
Asana Trigger: The remote server which is intended to receive the webhook responded with an incorrect status code: 403
Even though all the relevant firewall rules were disabled or set to bypass, the issue persisted. After digging deeper, I discovered the real problem was Cloudflare’s Bot Fight Mode.
Important detail: on the free plan, you cannot disable Bot Fight Mode per application or subdomain – it’s enabled globally. That means even if you configure bypass rules for your webhook subdomain, Bot Fight Mode can still interfere and cause 403 responses for Asana webhooks.
So the solution is:
If you are using Cloudflare (including Cloudflare Tunnels), disable Bot Fight Mode globally; or
Upgrade to a paid plan that allows you to turn off Bot Fight Mode for a specific app/zone and then disable it only for the application you use for webhooks.
After disabling Bot Fight Mode, the Asana Trigger node started working correctly and the 403 error disappeared. I’m pretty sure this behaviour will be the same for other webhook-based trigger nodes behind Cloudflare as well, so it’s worth checking this setting if you see similar 403 errors.
