I have a n8n workflow to send contacts to Clay via a webhook Then enrich them and send them back to n8n with HTTP When the emails and LinkedIn details are complete the data transfers to n8n If a row has any email of LinkedIn missing it fails I unchecked the Remove empty fields from the request and thought that would fix it but still not working Anyone successfully go data from n8n and back again who can help me out here ? TIA
For n8n to Clay webhook integration, you can send data into Clay programmatically and use HTTP actions to push enriched data back to n8n. This workflow is ideal for automating lead flow or enrichment jobs. To handle missing fields, you can set up Auto-Update on your Clay table to automatically process incoming data. The issue might be related to how your JSON payload is structured when sending data back to n8n. Could you copy and paste the JSON structure you're using in your HTTP request from Clay back to n8n so we can troubleshoot the formatting?
Fails as in how? What is the error?
The issue likely occurs because your HTTP enrichment runs before all data is populated. You can add conditional run settings to only execute when required fields contain data. Use the Required to Run toggle in your HTTP enrichment configuration - this ensures the action only runs when specific fields (email, LinkedIn) contain values, preventing failures on empty rows. For troubleshooting your JSON structure, could you copy and paste the JSON payload you're using in your HTTP request from Clay back to n8n? This will help identify any formatting issues causing the failures.
I have conditional run set up to only trigger when all data is enriched. It specifically fails when any columns I want to send are empty. I switched off the Remove empty fields from the request too but still fails
The issue occurs because your HTTP enrichment may be running before all data is populated, or the JSON structure contains null/empty values that n8n can't process. Use the Required to Run toggle in your HTTP enrichment configuration to ensure it only executes when specific fields contain data. You can also use conditional formulas to prevent enrichments from running on empty rows. Could you copy and paste the JSON payload you're using in your HTTP request from Clay back to n8n? This will help identify any formatting issues causing the failures.
I want to send all rows back to n8n even if they have empty columns
The "Remove empty fields from the request" toggle should handle this, but since you're still experiencing failures, the issue is likely in your JSON structure. When sending data with empty columns, ensure your JSON properly handles null/empty values. Dynamic variables from empty columns may not format correctly in JSON. For troubleshooting, could you copy and paste the JSON payload you're using in your HTTP request from Clay back to n8n? This will help identify the specific formatting issue causing the failures. The JSON structure must follow proper formatting rules - strings need quotes even when empty, while numbers and booleans don't.
Mike P. can you share the screenshot of the where it failed?
The issue is likely in your JSON structure when handling empty columns. When using dynamic variables from empty columns, they may not format correctly in JSON.
For proper JSON formatting with empty values:
** Strings need quotes even when empty: "email": ""
** Numbers and booleans don't need quotes: "age": null
When referencing dynamic variables using /column, you must follow JSON formatting rules. For dynamic strings, you still need quotation marks, but for dynamic number variables you don't.
Could you copy and paste the JSON payload you're using in your HTTP request from Clay back to n8n? This will help identify the specific formatting issue causing the failures.
## *Issue Description: I’m trying to send data from Clay to an n8n webhook using the HTTP column. The webhook works perfectly when all fields have data, but fails when any field is empty with the error: *“Body has the error(s): [Field Name] is blank” ## *What I’ve tried: **Disabled “Remove empty values”** setting - still fails **Used field picker interface** instead of raw JSON - still fails **Various JSON syntaxes** - all fail when fields are empty ## *Current JSON body that fails: ```json { "id": "{{ id }}", "email": "{{ Email }}", "linkedin": "{{ LinkedIn Personal URL }}", "clay_status": "{{ clay_status }}", "ProspectName": "{{ ProspectName }}", "CompanyOfProspect": "{{ CompanyofProspect }}" } ``` ## *The problem: When `Email` or `LinkedIn Personal URL` fields are empty (which happens when enrichment fails), Clay refuses to send the HTTP request. But I NEED to send the data even when enrichment fails so my n8n workflow knows about the failures. ## *Question for Clay support: **How can I configure the HTTP column to send data even when some fields are empty/blank?** The “Remove empty values” setting doesn’t seem to work for this use case. **Expected behavior:** Send the JSON with empty strings for blank fields like "email": "" ******
The "Remove empty fields from the request" toggle should handle sending empty values, but the issue is likely in your JSON structure.
When using dynamic variables with /column references, you must follow JSON formatting rules - strings need quotation marks even when empty, but numbers and booleans don't.
Try this corrected JSON structure: LBKS{ "id": "{{id}}", "email": "{{Email}}", "linkedin": "{{LinkedIn Personal URL}}", "clay_status": "{{clay_status}}", "ProspectName": "{{ProspectName}}", "CompanyOfProspect": "{{CompanyofProspect}}" }LBKSThe HTTP API has a "Remove null & undefined values" toggle that should prevent empty fields from causing failures.
Could you copy and paste your exact JSON payload so we can troubleshoot the specific formatting issue?
a screenshot of your inputs would help
I just pasted this above
gpt cant solve this for ure
The HTTP API has a "Remove null & undefined values" toggle that should handle empty fields. This is different from "Remove empty fields from the request" - make sure you're using the correct toggle.
For JSON formatting with empty values, strings need quotes even when empty: "email": "", while numbers and booleans don't need quotes. When using dynamic variables with /column references, you must follow JSON formatting rules - dynamic strings still need quotation marks.
Could you copy and paste your exact JSON payload from the HTTP column so we can troubleshoot the specific formatting issue?
