Troubleshooting Input Data Errors in Column Fields

When entering data in the input field, follow these JSON formatting rules to avoid errors: 1. For text/string values: • Always use double quotes around both the key and value • Example: "name": "John" 2. For numbers: • Use quotes for the key, but not for the number value • Example: "age": 30 • Exception: If you have numbers with trailing zeros (like 0004), put them in quotes 3. When using dynamic column values: • Include quotes around the dynamic column tag for string values • Create a Formula column first if you need to combine plain text with dynamic valuesHere's a correct example: LBKS{ "name": "John", "age": 30 }LBKSIf you're still having trouble, you can validate your JSON format using JSONLint. 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?

Is that what you were looking for?

The value you should enter depends on the data type you've selected for your column. Here are the supported data types and their corresponding values: • Text: Any text or string input• URL: Valid web links• Checkbox: True/false values• Select: Choose from predefined tags• Number: Numerical values only• Date: Date and time values• Currency: Monetary amounts• Email: Valid email addresses• Image from URL: Image URL linksMake sure to follow these formatting rules: • For text/string values: Use double quotes• For numbers: No quotes needed (except for numbers with trailing zeros)• For dynamic column values: Include quotes around the dynamic column tagIf you're still getting errors, check that there are no extra spaces or hidden characters in your input. Sources: Table columns overview | Documentation | Clay University HTTP API integration overview | Documentation | Clay University

Was that helpful?

Based on your error message, it looks like there's an issue with JSON formatting in your input. Here's how to fix the "invalid-input" error: 1. Make sure all text keys and values are surrounded by double quotes 2. Check for proper JSON syntax: • Use commas to separate key-value pairs • Remove any trailing commas • Ensure proper placement of brackets • Remove any extra spaces or hidden charactersHere's the correct JSON format to follow: LBKS{ "key": "value", "another_key": "another_value" }LBKSTo troubleshoot: ** Copy your JSON into a text editor to check for hidden characters ** Use a JSON validator like JSONLint to verify your format ** If using dynamic column values, make sure they're properly quotedCommon mistakes to avoid: ** Missing quotation marks around text ** Extra commas where they shouldn't be ** Improperly formatted special characters 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?

Was that helpful?

Here's the correct JSON format for input data: 1. For text/string values: • Use double quotes around both keys and values • Example: {"name": "Sam"} 2. For numbers: • Use quotes around keys, but not around number values • Example: {"age": 30} • Exception: Numbers with trailing zeros (like 0004) need quotes 3. For dynamic column values: • Include quotes around the dynamic column tag for string values • Example: {"email": "##{{email field}}"}Common formatting rules: ** Use commas to separate key-value pairs ** Remove any trailing commas ** Ensure proper placement of brackets ** Avoid extra spaces or hidden charactersHere's a complete example: LBKS{ "name": "Sam", "age": 30, "email": "[sam@clay.com](mailto:sam@clay.com)" }LBKSIf you're still getting errors, try pasting your JSON into a validator like JSONLint to check the format. Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?

Was that helpful?

When mapping column data to send to Apify, follow this JSON format in the Input Data section: 1. For column tokens (dynamic data from your Clay table): • Keep the key in quotes • Do not put quotes around the column token itself • Use the ##{{column name}} syntaxHere's the correct format: LBKS{ "email": ##{{email field}}, "name": ##{{name field}} }LBKSMake sure to: ** Use proper JSON formatting with curly braces ** Include commas between key-value pairs ** Keep the keys in quotes ** Don't wrap the column tokens (##{{...}}) in quotes Sources: Apify integration overview | Documentation | Clay University Run Apify Actor with Apify

Was that helpful?

For mapping the person_linkedin column to Apify, use this JSON format in the Input Data section: {"linkedinUrl": ##{{person_linkedin}}}Make sure to: ** Keep the key ("linkedinUrl") in quotes ** Do not put quotes around the column token (##{{person_linkedin}}) * Use proper JSON formatting with curly bracesWhen referencing column tokens (dynamic data from your Clay table), the key should be in quotes, but do not wrap the column token itself in quotes. Sources: Apify integration overview | Documentation | Clay University Run Apify Actor with Apify

Did that answer your question?

You're getting this error because dynamic string variables need to be enclosed in quotation marks. Here's the correct JSON format for your LinkedIn URL: {"linkedinUrl": "##{{person_linkedin}}"}Make sure to: ** Keep the key ("linkedinUrl") in quotes ** Put quotes around the column token (##{{person_linkedin}}) * Use proper JSON formatting with curly bracesIf you're still having trouble, try copying your JSON into a text editor to check for any hidden characters or extra spaces that might be causing the error. Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University

Is that what you were looking for?

When using LinkedIn data with Apify, you'll need to include both cookie and proxy settings in your JSON input. Here's the complete format: {"linkedinUrl": "##{{person_linkedin}}","cookie": "YOUR_LINKEDIN_COOKIE","proxy": "YOUR_PROXY_CONFIGURATION"}Please note that using scrapers like Apify with your LinkedIn cookies could put your account at risk since these tools use your cookies during the scraping process.If you need to scrape LinkedIn data safely, we recommend using our built-in enrichment options instead, which don't require cookies or proxies.

Did that answer your question?

Instead of using Apify with proxies and cookies which could put your LinkedIn account at risk, we recommend using our built-in enrichment options to safely get LinkedIn data. These native enrichment features don't require proxy configuration or cookies and are designed to work securely within Clay.

Is that what you were looking for?

For scraping LinkedIn profile posts, we offer Claygent - our built-in AI research tool with web access. For best results when using Claygent, you should use advanced AI models like Argon or OpenAI's GPT 4o.Please note that since our post data comes from public web scraping and we don't connect directly to LinkedIn accounts, some limitations may apply: ** Posts might be missed if someone hasn't been active recently ** Private accounts may not be accessible * Content that hasn't been publicly scraped recently might not be available

Is that what you were looking for?

Hi Aditya K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Looks like you're still looking for help. 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!