Debugging Infinite Loop in Clay API for Serper.Dev Search Parameters

Hi - I have a bit of a technical question, I am working on the Serper.Dev Clay API, I have created the following from Server. The problem is when I add the "search parameters" as columns and then update the body to map the columns, it creates an infinite loop and error. Have tried to de-bug multiple times and cannot figure it out, any help?

33 comments

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Muhammad S.
·
·
This happens when you are trying to add an input that is connected to the output of your column. i.e you are passing an output of seper.dev to the input of serper.dev Can you check where the parameters query string and location string are coming from?
Muhammad S.
·
·
Ensure query string and location string are not dependent on the output of serper.dev
Griffin D.
·
·
Hi thanks for the reply, it appears that the query string and location string are coming from the HTTP API, how would I fix this problem specifically, in clay or in serper.dev? I am unsure
Muhammad S.
·
·
You are passing the output of google search as an input to it, you should avoid doing that and it will work just fine.
Muhammad S.
·
·
You can create a new column of HTTP api and then pass the query string to it and it should be ok
Griffin D.
·
·
So I changed the output of the google search as an input and made the columns just regular text columns but am still recieving the error code https://app.clay.com/workspaces/263283/workbooks/wb_4vN5BnBERsoG/tables/t_dCP5HqzREwV3/views/gv_CxHbnvgZTQAQ
Muhammad S.
·
·
i can not access your table (only clay team can do that.). If you can share screenshot of your table I can provide you more information
Griffin D.
·
·
Muhammad S.
·
·
Thank you, can you scroll down the google search column and show me the run settings ?
Griffin D.
·
·
Muhammad S.
·
·
Nice, can you click on the error and send me the screenshot to see the details of your error? It is because your inputs are empty
Griffin D.
·
·
wouldnt my inputs be from the serper dev?
Muhammad S.
·
·
No, why? that was the problem originally
Muhammad S.
·
·
You need to build a query to pass it to serper.dev

Griffin D.

Clay received a 400 error from the API with Content: {"message":"Missing query parameter","statusCode":400}

Muhammad S.
·
·
please see my video to properly integrate it: https://www.youtube.com/watch?v=6PSKMTU9rKY
Griffin D.
·
·
followed video, thanks for sharing, now getting this error: Failed to parse body input
Muhammad S.
·
·
Can you show me your body?
Griffin D.
·
·
I am going to try the query string
Muhammad S.
·
·
Add double quotes around query and location column:
Muhammad S.
·
·
Muhammad S.
·
·
""
Griffin D.
·
·
ok i have run to many times, i have to try again in a few minutes
Muhammad S.
·
·
you can duplicate the column and run again
Griffin D.
·
·
good idea, will d
Griffin D.
·
·
nice it worked
Griffin D.
·
·
Thank you so much, i have learned a lot now
Muhammad S.
·
·
great!
LuisArturo
·
·
Hey there Griffin thanks for reaching out and appreciate you jumping in Muhammad! As I believe Muhammad may have mentioned already, if the initial column is returning an infinite loop message because the output is being used as the input, then you can can create a second HTTP API column that can take in those column values instead to avoid the loop.
Griffin D.
·
·
Sounds great thanks for letting me know Luis! Now I am working on performing a multi page serper querie via Make. I have followed most of the steps and it says "200" in my HTTP API with the Make webhook as an end point but I am receiving bad data as you can see via the screenshots, any idea if this is on the clay side or the Make side?
LuisArturo
·
·
Hey there Griffin thanks for sharing this, this looks to be an error on Make's side, as the call from Clay was successful, since you received a 200 response which means that the call was prompted correctly.
Channeled
APP
·
·
Hi Griffin D.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: