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

Issue with HTTP [WCN] Client Notification Enrichment Inputs

Why is the HTTP [WCN] Client Notification enrichment in https://app.clay.com/workspaces/13461/workbooks/wb_boZRCnUvnoXk/tables/t_X6EXwZ26gVVm/views/gv_fGmy8buGUZpU showing: Some Inputs Are Missing. When the inputs in questions are not required to run the column?

👀1

29 comments

David
·
·
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
·
·
I did all of the following and the error still persists
David
·
·
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.
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
·
·
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
·
·
Hey Arturo
David
·
·
We manually change it from Clay.FormatForJSON to JSON.Stringify as we constantly run into issues with this new Clay JSON function
David
·
·
Do you think that’s the issue here?
Arturo O.
·
·
Oh, I see! Not entirely certain, I wasn't able to reproduce this specific issue related to "required to run", if you run the linkedin waterfall does it let it continue? Also, feel free to share any related issues you run into with clayformatforjson, so we can bring them up with the team
(69 kB)
(63 kB)
David
·
·
Haven’t tested yet. Will do in a second and see. Just by the error message itself Clay seems to be upset about the fields being completely empty compared to the other ones
Arturo O.
·
·
Yup!! Just ran a test in another table and that one ran into the error message. I'll create the ticket or check the status if it's been reported already, appreciate the flag, David.
David
·
·
Thanks! I could a workaround for now and just fill it with a “no data” string if we dont have data for this. If you can keep me updated on this, that be great Arturo!
Arturo O.
·
·
Alrighty, will do! There is a ticket following this issue and have linked this conversation so we can update you as soon as the team confirms it was addressed. Can't say much about an ETA but I've pinged the team for some follow ups. Will keep you posted!
David
·
·
Thanks Arturo O. , always class with you 🤝🏼
🤝🏽1
1
Bruno R.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.
Channeled
APP
·
·
Hi David! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
David
·
·
Bruno R. empty values with JSON.stringify are still not wrapped properly in quotes, even after a refresh
Bo (.
·
·
Hey! Quick question, did you create a new column after the fix or is it the same old one? Can you also share what specific empty values aren't being wrapped in quotes? I'm checking and it seems like it's all worked out (no errors) Let me know and I'll help get this sorted out for you. Thanks!
David
·
·
I duplicated the table
Bo (.
·
·
Can you try starting fresh with a new enrichment instead (Enrichment Panel > HTTP API) and then add all of the values manually instead of copying the old setup since it'll also copy it's configuration. This way you'll get the latest version. Creating a new HTTP API table would copy over the old configuration, so let's avoid that. Let me know if the new enrichment works better for you.
David
·
·
Will try
Daniela D.
·
·
Hey David! Just checking in. Let us know if you still run into any issues with the HTTP API configuration.