Webhooks, CORS and 500 error

Questions
1

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • cloud 1.88
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n viaCloud
  • Client uses MacOS

I am trying to call n8n webhook from the app build in Lovable and in the network tab of the browser I see the following errors and the n8n workflow never gets triggered. I searched the web and this community but couldn’t find a solution. I am new to n8n and I probably missing that is very simple and stupied. I will change the api_key after I solve this problem :slight_smile:

image
image672×400 54.1 KB

image
image836×829 145 KB

I have this variables set in n8n (not sure if they work as I am on a starter plan)

image
image1255×818 85 KB

2

Hi, I’m not sure for the cloud version but normally under the webhook trigger there is an options section which contains a CORS option

You could try to set I to * for testing purposes.
After that to whatever you need

Also not sure if you explicitly have to add the options method as allowed. By default the only allowed method is GET. If not you need to go to settings and toggle allow multiple. And then set whatever is needed

Regards
J.

3

thanks, I tried this setting, did you mean it?

didn’t help either

4

Btw you need to change your method to post… Or allow multiple. Your request was a post instead of get. Like I mentioned. Go into the settings tab , select allow multiple and set get / post / options (if that even exists I’m not behind a computer)

Reg
J.

5

yes, it was with Post I was playing with settings and pasted the outdated code, sorry

6

Are you using header Auth? Or is this a mistake? Please disable it for now.

7

I do use Auth header, I tried going with None, doesnt seem to make a difference

8

Does as request through postman/curl/… work?

9

This CORS tester might help to test whether you have the CORS settings correct.

1 Like
10

You are genius :slight_smile:
so it seems to me that previously I was setting that I expect knowledge in the Node Path, but then I moved to Post and as a solution I removed knowledge from the Path and it started working
here is the updated flow

2 Likes
11

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.