Troubleshooting Data Transfer Issues from Clay to Instantly

·

Hi team, I've noticed that when sending data from Clay to Instantly, some fields occasionally come through empty, even though they are correctly populated in Clay. Could you help me understand why this might be happening and how to ensure all fields transfer consistently? Thanks in advance!

3 comments

Channeled
APP
·
·
When sending data from Clay to Instantly, fields may appear empty for a few reasons: 1. Integration fields showing "run condition not met" in Clay will appear blank in the CSV or when transferred to other systems. 2. If you have the "Remove null and undefined values" option enabled in your HTTP API integration, any fields that are empty, null, or undefined will be removed from the request. To ensure consistent field transfers: ** Double-check that your column names match exactly what Instantly expects (using snake_case format). ** Verify you're using the correct column names from your Clay table. * Create a dedicated view with only the essential data fields you need to transfer. If you're still experiencing issues, try refreshing your browser or checking if the "missing input" error appears, which indicates a column name mismatch.
Sources: Push Data To Your Email Sequencer [Automated Outbound] - Clay University HTTP API with JWT authentication | Documentation | Clay University Download as a CSV [Clay 101] - Clay University
Emre S.
·
·
Rerun the instantly coloum, the rest of the table is still loading, the instantly colum pushes to instatntly once the email is found, not after everything else is finished
Owen C.
·
·
Hey Amboga, thanks for reaching out! Would love to take a closer look here. Do you mind sending the link (url) to the table so we can take a look?
(52 kB)
🙌1