Issue with HTTP [WCN] Client Notification Enrichment Inputs

David L. · 2025-02-17 18:52:08.579047+00

Why is the HTTP `[WCN] Client Notification` enrichment in showing: _Some Inputs Are Missing_. When the inputs in questions are not required to run the column?

Issue with HTTP [WCN] Client Notification Enrichment Inputs | Clay

David L.
·
·
Specifically these 2: Body has the error(s): [Final] Facebook is blank [WLM] Instagram is blank
Channeled
APP
·
·
When you see "Some Inputs Are Missing" errors for fields like "[Final] Facebook" and "[WLM] Instagram", this is likely related to how the HTTP API enrichment processes empty or null values. To resolve this, you can: 1. Toggle the "Remove null and undefined values from the request" option in your enrichment settings. This will prevent sending blank values to the API. 2. If you still encounter issues, check your body section formatting: • Ensure all keys have proper double quotes • Check for correct punctuation and syntax • Look for any hidden characters that might be causing issues You can also validate your JSON structure using a JSON validator to ensure proper formatting of all fields, even optional ones.
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?
Channeled
APP
·
·
Is that what you were looking for?
David L.
·
·
I did all of the following and the error still persists
David L.
·
·
Even if I click on the "I'm aware....". It vanishes, and as soon as I click somewhere else it comes back up again and I have the error.
Loading attachments
Channeled
APP
·
·
The "Some Inputs Are Missing" error for "[Final] Facebook" and "[WLM] Instagram" in the HTTP "[WCN] Client Notification" enrichment might persist due to JSON formatting issues. To resolve this: 1. Ensure all text values are in quotes 2. Remove any extra commas at the end of lines 3. Double-check your data format before sending If the issue continues, try pasting your data into a JSON validator like JSONLint to spot and fix any formatting problems. Can you share a snippet of your JSON body for the HTTP enrichment, focusing on the "[Final] Facebook" and "[WLM] Instagram" fields?
Source: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?
Channeled
APP
·
·
When you're seeing a persistent "Some Inputs Are Missing" error that keeps reappearing even after clicking "I'm aware...", try clearing your browser cache and refreshing the view. This is a common issue with missing input fields in enrichments, particularly when working with optional fields like "[Final] Facebook" and "[WLM] Instagram". Even if these fields aren't required to run the column, the error message may persist due to browser caching issues. To clear your browser cache: ** Mac users: • Chrome/Firefox: Press Cmd + Shift + R • Safari: Press Cmd + Option + R ** PC users: • Chrome/Firefox/Edge: Press Ctrl + F5
Source: Push Data To Your Email Sequencer [Clay 101] - Clay University
Channeled
APP
·
·
Is that what you were looking for?
David L.
·
·
Did this as well, error still remains
Channeled
APP
·
·
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!
Muhammad S.
·
·
can you share screenshot of your inputs?
Arturo O.
·
·
Hey David, thanks for reaching out! Happy to help. Will have to check out why the required to run but I noticed the LinkedIn URL waterfall finder hasn't run yet so maybe it was expecting that flow to determine if Facebook actually existed or not, but can't say the same thing about the instagram column. However, looks like this is an older HTTP template, correct? It's still using the previous HTTP config with JSON.stringify, but the team updated to a new action to better and gracefully handle a lot more edge cases with ClayFormatForJSON -> here's this video on how I quickly updated the column to the current action format if it helps: https://www.loom.com/share/9319afd9ddb24036be24b5d25571fa89
(16 kB)
David L.
·
·
Hey Arturo
David L.
·
·
We manually change it from Clay.FormatForJSON to JSON.Stringify as we constantly run into issues with this new Clay JSON function
David L.
·
·
Do you think that’s the issue here?

29 comments