Google Custom Search dont scrap the information

Hello everyone!

I have an error in the HTTP node.
I search for a person’s name using Google’s “Programmable Custom Search” API to find information about that person. In this case, I am using myself as a test subject.

When I search for my name on my own, Google returns several results, but when I do it with n8n and the Programmable Search API, it returns no results.
What’s more… it changes my last name in the output.

Integration Background:
API Key and CX:

I generated an API key and a custom search engine via the Google Cloud Console. Testing with the URL in the browser works perfectly.

I’m sending you a screenshot to see if anyone can shed some light on this.
I share a Screenshot:

Number 1 is my last name.

Number 2 says there are no results.

Number 3 changes the last name.

As you can see, it comes from a Custom Fields node, and it also gets the name right there.

Hey @Dazaga hope all is well. Welcome to the community.
What if you send a similar request with curl or postman for example, does it produce more results?

1 Like

You mean in the method?
I dont see where…

I mean the same request, only send it not from n8n, but from any different tool which allows sending http requests.

In Postman the request its fine!! :thinking:

What is different about this request? Unfortunately I cannot inspect this myself, as you are only providing screenshots, so you have to explain the difference to me :slight_smile:

1 Like

Yes, sorry!

The difference is that in Postman I entered the name directly in the field called “q” and in n8n I entered what I showed you in the screenshot.
It’s the same as what I brought from the previous custom fields node.

I meant what is the different in terms of the resulting JSONs. One is bigger? Have more findings? Have more accurate findings?

Sorry for not responding, Jabbson. I’ve been too busy these days.
I don’t quite understand the question.

No problem at all.

Let me elaborate. When you make the same request (same headers, same body, same everything) in postman and http request - how are the results different, what is different about them - one is longer, or has more details? Please include both requests - from postman and from n8n as well as the full results for us to compare.

There must be something different in how these requests are sent.

1 Like

I’ve solved it.
The problem is that in the variant named “q” you only have to enter the Json value, i.e. in this case {{$json.nombre_persona_buscada}} and not the entire comment I showed you in the previous screenshot.
I imagine it’s because it’s a programmable Google search node and I just have to enter the word or name you want to search for.
Thanks for your help! :blush:

Now I have the problem that I don’t want it to include the search on Facebook. I’ve restricted the Facebook page in Google’s programmable search engine, but it doesn’t work.

Have you done anything with Google programmable search engine?