Trigger returns 403 error when testing even though response contains data

  • 12 May 2021
  • 5 replies

I’m just testing a trigger using polling. It returns a 403 error. However, in the http tab, I can see all my data came in the response content. So, clearly something else is going on…


Any pointers will be appreciated.

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

5 replies

Userlevel 7
Badge +14

Hi @jojobar 

Are you able to provide screenshots of how your Zap step is configured as well as the returned error?

Here it is:



Also wanted to mention, I did not create a zap, I was just testing the trigger.

Userlevel 7
Badge +9

I’d like to rule out the embedded test tool just being weird. Try making a Zap with that and testing in the editor. Check out the resulting logs in the Monitor section from the left hand nav. This will give you ground truth about how your request is actually behaving. 

What auth config are you using? Assuming “API Key”… another thought is to examine your auth configs test request. Wondering if some other request other than the one you’re trying to test is failing and that’s what you’re seeing the logs for, but that’s a shot in the dark without actually looking at the project.  

Let me know what you learn there.

Yes auth test was working just fine. 

I will take your advice and test with a zap and report back here.