N8n - HTTP request node: Input - No fields - item(s) exist, but they're empty

Questions
1

Hi Everyone!

I am quite new to n8n and one of my first projects is to build a chatbot that can be embedded on a website. Bellow is a very simple workflow that I created that seems to be quite functional, except for it does not allow the chatbot to answer questions that are related to the content of a website. I tend to get answers such as “I could not find specific information about the website’s content from the initial search. Could you clarify what topic or type of information you want to find on the website?”

Also, I noticed that in the HTTP request the Input returns the following: “No fields - item(s) exist, but they’re empty”. In case you know how to fix it, would you please advise?

I highly appreciate any help from more advanced n8n users!

Many thanks!

image
image886×474 45.7 KB

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

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hello @Tester Hope you are well ,
The issue you are facing is beacuse website contents are in HTML format ,
while fetching data from a website using HTTP Request node returns none,
That is why it is not being used by this AI Agent ,
& also you are calling POST request in HTTP Request node ,

I think you should try GET method & see if it is working or not .

Let me know if it works or not .

3

Thanks for the guidance. I discovered the problem was that I was using the Webhook URL instead of the dataset URL. Once I updated the HTTP Request node to use the dataset URL, the response came back as valid JSON and the node output populated correctly. Hopefully this helps anyone else running into the same issue.