Troubleshooting Multi-Page Serper Queries with Make.com

Griffin D. · 2025-03-17 21:09:00.133585+00

Hello everyone, I am using and for performing Multi-page Serper Queries via . When I write in the request body of "q": "/Query" it provides a body parse error. when I enter "top restaurants in NYC" it works perfectly but i do not want to hard code each line for all the cities I am going to use for this project. any help?

Troubleshooting Multi-Page Serper Queries with Make.com | Clay

6 comments

· Sorted by Oldest

Channeled
APP
·
·
The "failed to parse body" error typically occurs when there's an issue with the JSON formatting in your request body. To resolve this without hardcoding each city, you can try the following: 1. Ensure your query is properly formatted within double quotes. 2. Use a formula or variable to dynamically insert the city name. 3. Double-check your JSON syntax, including commas and brackets. For a more accurate diagnosis, could you please copy and paste the exact JSON you're using in your request body? This will help us troubleshoot the specific formatting issue you're encountering.
Sources: HTTP API integration overview | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?
Griffin D.
·
·
Loading attachments
Channeled
APP
·
·
To resolve the "failed to parse body" error for dynamic queries, ensure proper JSON formatting: 1. Surround your dynamic query with double quotes: "q": "/Query" 2. If combining text with a dynamic variable, use a formula to merge them first 3. Check for correct punctuation, avoiding extra spaces or commas 4. Validate your JSON structure in a text editor or JSON validator Could you please copy and paste your exact JSON from the request body? This will help us troubleshoot the specific formatting issue you're encountering.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?
Bo (.
·
·
Griffin - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Summiya B.
·
·
Make sure the variable Query is correctly passed from a previous module. Remove the / before Query and just use "q": "{{Query}}" (assuming Query is a mapped variable in Make.com). If the variable is inside an array or object, ensure it's properly structured in JSON format. also put your api key in header section.
Channeled
APP
·
·

Channeled
APP
·
·
The "failed to parse body" error typically occurs when there's an issue with the JSON formatting in your request body. To resolve this without hardcoding each city, you can try the following: 1. Ensure your query is properly formatted within double quotes. 2. Use a formula or variable to dynamically insert the city name. 3. Double-check your JSON syntax, including commas and brackets. For a more accurate diagnosis, could you please copy and paste the exact JSON you're using in your request body? This will help us troubleshoot the specific formatting issue you're encountering.
Sources: HTTP API integration overview | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?
Griffin D.
·
·
Loading attachments
Channeled
APP
·
·
To resolve the "failed to parse body" error for dynamic queries, ensure proper JSON formatting: 1. Surround your dynamic query with double quotes: "q": "/Query" 2. If combining text with a dynamic variable, use a formula to merge them first 3. Check for correct punctuation, avoiding extra spaces or commas 4. Validate your JSON structure in a text editor or JSON validator Could you please copy and paste your exact JSON from the request body? This will help us troubleshoot the specific formatting issue you're encountering.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?
Bo (.
·
·
Griffin - Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
Summiya B.
·
·
Make sure the variable Query is correctly passed from a previous module. Remove the / before Query and just use "q": "{{Query}}" (assuming Query is a mapped variable in Make.com). If the variable is inside an array or object, ensure it's properly structured in JSON format. also put your api key in header section.
Channeled
APP
·
·