Another one me from me - I sometimes run into the issue of an enrichment waterfall not behaving as expected:
All columns run, as opposed to waiting for the previous column to find a match
The merge column stays empty
Anything I'm doing wrong? Table here
If your waterfall enrichment isn't working as expected, here are a few key points to check:1. Verify the waterfall setup: • Make sure you've properly configured your API keys • Check that the waterfall "parent" column is correctly structured • Confirm your validation settings 2. Understanding how waterfalls work: • Waterfalls run providers sequentially, not simultaneously • If one provider doesn't find the specific data point you need, it will move to the next provider • All provider data ultimately feeds into one final result columnTo set up a waterfall correctly:1. Right-click "Add Column" > "Add Enrichment" 2. Search for "Waterfall" 3. Select your desired data point 4. Click "Save" and runIf you're still experiencing issues, you may want to test the enrichment on a small sample of rows first to identify any potential setup problems. Sources: Enrich Companies (Waterfalls) [Clay 101] - Clay University Waterfall
Still on the topic of waterfalls not behaving as expected - getting this error when trying to run a phone enrichment (same table)
If you're getting an error with your phone enrichment waterfall, it's likely due to a "failed to parse body" error. Here's how to fix it:1. Check that all text values are properly enclosed in double quotes 2. Remove any extra commas at the end of your inputs 3. Make sure there aren't any extra spaces, colons, or brackets in your syntax 4. If using dynamic columns, ensure they're properly quotedFor a quick fix, you can paste your data into a JSON validator like JSONLint to spot formatting issues. If you're combining plain text with dynamic column tags, first create a Formula column to combine them, then include that column (with quotes) in your body tag. Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API with JWT Authentication - Clay University
Problem #1 is solved - it had to do with the email validation provider not working for me. still curious about problem #2 - why phone waterfall is failing
The "failed to parse body" error typically occurs when there's an issue with how your data is formatted in the Body section of your enrichment. Here's how to fix it:1. Check that all text values are properly enclosed in double quotes 2. Remove any extra commas at the end of lines 3. Ensure proper punctuation and syntax, including correct spaces, colons, and brackets 4. Look for hidden characters by copying your body text into a plain text editorFor example, instead of::LBKS{LBKSname:: John,phone: 1234567890,}Use::LBKS{LBKS"name":: "John","phone": 1234567890}If you're still having trouble, try using a JSON validator like JSONLint to check your data format. Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API with JWT Authentication - Clay University HTTP API - Clay University
Fantastic! I'm here if you need any further assistance with our app or services.
Hi Laurent B.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
.png&w=3840&q=75){kind=logo}
