Clay Icon

Error: JSON Output Failure in Clay Table View

Β·
Β·

Getting a The output failed to parse as JSON. Please contact Clay support. in the this table. Worked perfectly fine just yesterday.

  • Avatar of Channeled
    Channeled
    APP
    Β·
    Β·

    This error indicates there's an issue with JSON formatting in your data. Here's how to troubleshoot: 1. Check these common JSON formatting issues: β€’ Ensure all text values are in double quotes β€’ Remove any trailing commas β€’ Check for proper syntax with colons and brackets 2. Additional troubleshooting steps: β€’ Look for extra spaces or hidden characters β€’ Verify proper comma separation between keys β€’ Double-check that dynamic column values are properly quotedFor a quick validation, you can paste your data into JSONLint to identify any formatting issues. Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API integration overview | Documentation | Clay University

  • Avatar of Channeled
    Channeled
    APP
    Β·
    Β·

    Did that answer your question?

  • Avatar of Channeled
    Channeled
    APP
    Β·
    Β·

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

  • Avatar of Channeled
    Channeled
    APP
    Β·
    Β·

    Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.

  • Avatar of David
    David
    Β·
    Β·

    Hey Arturo O. - when you have a breather, mind looking into this one?

  • Avatar of Channeled
    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!

  • Avatar of Bruno R.
    Bruno R.
    Β·
    Β·

    Hey there, thanks for reaching out! I'm looking into this now. It looks like the table contents of the workbook you shared have been deleted: link. Do you know who might have removed them?

  • Avatar of David
    David
    Β·
    Β·

    Yeah I found a workaround. not the prettiest, but shortening the number of keys of the expected result JSON fixed the issue. Also duplicated the table as it was buggy.

  • Avatar of David
    David
    Β·
    Β·

    You can see it as resolved, but you might want to look into JSON outputs that are too big causing trouble. Here we had a JSON array with 61 entries, each with 5-6 keys.

  • Avatar of Bruno R.
    Bruno R.
    Β·
    Β·

    Got it happy to hear you were able to resolve this! Let us know if this issue pops up again, I'd be happy to take a look at what may have gone wrong here.

  • Avatar of Channeled
    Channeled
    APP
    Β·
    Β·

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