Unexpected Changes in Clay Table After HTTP API Enrichment | Clay

Unexpected Changes in Clay Table After HTTP API Enrichment

something really weird is going on in my clay table - I ran an HTTP API enrichment last night and when i came back in this morning i noticed all the values had changed across all those enriched rows.

7 comments

Channeled
APP
·
·
When you run an HTTP API enrichment in Clay, the values in the enriched rows will update based on the latest data returned from the API. If you have the "auto-update" option enabled, the enrichment will automatically refresh whenever new rows are added or when the enrichment is re-run, which can cause all values in those rows to change if the API returns different data or if the enrichment criteria have changed. If you want to prevent automatic updates, you can toggle off the auto-update option in the enrichment settings. If you suspect an issue with the API response or the enrichment configuration, you can copy and paste your JSON or enrichment setup here for further troubleshooting assistance.
Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
Nir B.
·
·
oh nvm i figured it out
Nir B.
·
·
actually no sorry i did not
Nir B.
·
·
thought i realized what was going on - still a mystery
Bruno R.
·
·
Hi Nir, thanks for your message - taking a closer look at this now.
Bruno R.
·
·
Can you share the url to the table you're seeing this behavior in? Is there anything which may have caused a re-run in the configuration, like updated inputs or other input changes upstream of the http api action you're describing?
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.