Troubleshooting Workbook and API Call Issues in Zapier

Loh Y. · 2025-11-26 02:25:28.2149+00

I need help troubleshooting this. • Workbook here (https://app.clay.com/workspaces/515577/workbooks/wb_0sxrzp2qvE9cvi4FJMc/tables/t_0sxrzp2YWEjmVDZEK3y/views/gv_0swz4rz6qBXD8g5FG7r). • I have the same exact setup inside Zapier and the api call works.

Troubleshooting Workbook and API Call Issues in Zapier | Clay

Clay Support
APP
·
·
The "incorrect header check" error typically indicates a formatting issue with your headers or body configuration.
Since you mentioned the same setup works in Zapier, can you copy and paste the JSON body from your HTTP API configuration in Clay? This will help me spot any formatting differences.
Also, click into the specific error cell to see if there are more detailed error messages that might give us additional clues.
Before we dig deeper, try using Sculptor (the AI tool in the top-right corner) - click "Troubleshoot with AI" and paste your error message. It's great at diagnosing API configuration issues.
Loh Y.
·
·
how do i find the json body of my api configuration?
Clay Support
APP
·
·
To find your JSON body in Clay's HTTP API configuration:
1.
Click on your HTTP API column in your table
2.
Click the settings/edit icon (usually a gear or pencil icon)
3.
Look for the "Body" section in the configuration panel
The JSON body will be displayed in a text field where you can see exactly what data you're sending.
Since you mentioned formatting issues, can you copy and paste your current JSON body here? I can help spot any formatting problems that might be causing the "incorrect header check" error.
Loh Y.
·
·
It looks like this. im doing a get api call and there's no boyd
Loading attachments
Clay Support
APP
·
·
Perfect! You're right - GET requests don't need a body, so that's not the issue.
The "incorrect header check" error is likely coming from your headers. I notice you have Content-Type: application/json set, but for GET requests you typically don't need this header since you're not sending JSON data.
Try removing the Content-Type header and keep only your Authorization header. That should resolve the formatting issue.
If that doesn't work, click into the specific error cell to see if there are more detailed error messages.
Clay Support
APP
·
·
Is that what you were looking for?
Loh Y.
·
·
Still getting this
Loading attachments
Clay Support
APP
·
·
The -3 "incorrect header check" error suggests there might be hidden characters in your configuration.
Try this:
1.
Copy your entire Authorization header value into a plain text editor first
2.
Look for any invisible characters
3.
Clean it and paste back into Clay
Also, since you're doing a GET request, try removing the Content-Type header entirely - it's not needed for GET calls.
Click "Troubleshoot with AI" in that error popup and paste your error message there - Sculptor is great at diagnosing these API issues.
Clay Support
APP
·
·
Did that answer your question?
Loh Y.
·
·
Nope. Huamn support pls
Clay Support
APP
·
·
I'm sorry for the trouble you're experiencing. I'll connect you to a human agent who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Mayato (.
·
·
Hi Loh, thank you for reaching out. I will be reviewing your table.
Mayato (.
·
·
I’ve checked your table, and it looks like the webhook is receiving data correctly. Are you still seeing the error on your side?
Loh Y.
·
·
Please chekc this video

23 comments