Lead Upload Timing Issues in Data Enrichment Process

I had a scenario where leads are being uploaded into instantly before all the previous fields and enrichments are done running. So, the result is not getting the complete lead data into clay since these leads are being uploaded before all the enrichments are done. Once all the enrichments are done running, it then seems to try to send that new data to Instantly and we end up seeing the skipped result. I tried to set this as the condition: !!{{Cleaned Company Name}} && !!{{Cleaned Company Name (Possessive)}} && !!{{Cleaned Job Title}} && !!{{Job Title Abbreviation}} && !!{{Job Role Responsibility}} && !!{{Primary Niche}} && !!{{Primary Niche (Plural)}} && !!{{PS Line}}

29 comments

Channeled
APP
·
·
To ensure leads are fully enriched before uploading to Instantly, you can use conditional runs in Clay. Here's how: 1. Add an Instantly enrichment to your Clay table. 2. In the enrichment settings, configure it to add leads to your campaign. 3. Set up conditional runs using AI formulas to filter rows based on specific criteria. 4. Include all necessary fields you want to sync (e.g., email, first name, last name, company name). 5. Use the "!!" operator in your condition to check if fields are populated. For example, your condition might look like: !!{{Cleaned Company Name}} && !!{{Cleaned Job Title}} && !!{{Primary Niche}} This ensures the enrichment only runs when all required fields are populated, preventing premature uploads to Instantly.
Sources: Guide: Ways to save Clay credits | Documentation | Clay University Push Data To Your Email Sequencer [Automated Outbound] - Clay University Trouble with Clay and Instantly Integration: Leads Not Syncing Properly | Clay Push Data To Your Email Sequencer [Automated Outbound] - Clay University
Michael L.
·
·
No I do not think this is working for me based on what I just explained
Bruno R.
·
·
Hi Michael, thanks for your message and sorry about the delay here! Happy to take a closer look at the run conditions for the instantly column you're describing here. Could you share the url to the table where you're seeing this issue pop up in?
Michael L.
·
·
Hi Bruno R. thanks for getting back to me on this. I DM'd you the URL
Bruno R.
·
·
Thank you Michael - for the future, feel free to drop table links in the chat directly, noone else will be able to access your table but the team at Clay. Can you clarify the exact conditions that you want to meet with your formula to run the instantly push here? That would be something along the lines of: if "PS Line generation" is empty then run column etc.
Michael L.
·
·
Okay, thanks for the clarification and taking a look at my table. I would only like the Instantly enrichment to run (or push the leads) if all other enrichment's (or columns) have finished running
Michael L.
·
·
The formula screenshot that I sent was my attempt to achieve this. My thought was to have some sort of condition that states "Only run if xyz is NOT empty" or something along the lines of that
Michael L.
·
·
But what I have experienced here is that the instantly Enrichment pushed the data into Instantly before all the columns were finished running and left out some of those "persoanlization" columns that I needed to have as custom fields in my campaign
Michael L.
·
·
Then I supposed, when the columns (for those specific rows) finished running, it tried pushing those leads to Instantly again and ran into the "Skipped, already in..." and did not update the leads data fields
Bruno R.
·
·
Got it! It looks like you're on the right track here:
(139 kB)
I suggest that you list the exhaustive columns which you want to be completed before you run the instantly push in this AI prompt - the run conditions for this should be met once you add all the required inputs to run, and click on generate formula. Let me know if you run into any issues with configuring this!
Michael L.
·
·
I am not sure what you mean by exhaustive columns? The column that I created from the JSON data that came from the enrichment or the enrichment column itself?
Michael L.
·
·
And what I had done in the formula is list out all the JSON data that come from the enrichment's. Those are the columns that need to have data in them before any rows are pushed to Instantly.
Michael L.
·
·
So, if you are referring to creating a list from the JSON data the comes in from the enrichments for the ones I want to be "completed" before running the instantly push, I have the coulumns listed there in the screenshot you sent. How would you suggest I edit the formula or change it?
Bruno R.
·
·
Hi Michael, sorry about the confusion here, I mean all columns for which runs you want to wait to be completed before pushing data to instantly. Let me know if this makes sense.
Michael L.
·
·
Yes it does, I have them listed there
Michael L.
·
·
For more context, I noticed that for the columns that have the "Skipped, already in..." result from Instantly don't have the data from the "Job Role Responsibility" in those leads custom fields when I go in and look at the lead in Instantly
Michael L.
·
·
https://app.clay.com/workspaces/257657/workbooks/wb_amaZbpzJcSrq/tables/t_HFvu5VxvGxJd/views/gv_hBKkXVpYB42G
Bruno R.
·
·
Hi Michael - I just configured a "data completeness" formula for you - which you can reference the run conditions of you instantly push. You'll just have to paste this formula in the run conditions of your instantly column and this should simplify and solve your issue: {{Data Completeness}} === true
🔥1
Michael L.
·
·
Amazing! Thank you
Bruno R.
·
·
Happy to help Michael!
Michael L.
·
·
Hi Bruno R., I ran the new columns but for some reason the "Skipped, already in..." is still showing up. Does this mean that the Instantly enrichment checks for duplicates and I already have this lead in my workspace?
Bruno R.
·
·
That's correct! It looks like you already uploaded those leads to Instantly here.
Michael L.
·
·
Okay nice! Is there any feature to turn this off?
Michael L.
·
·
When uploading CSVs to instantly it allows you to select how Instantly will check for duplicates at either the workspace, a list, or at the campaign level. Curious if this is possible through your Instantly API. If I could select "check for duplicates within XYZ campaign" that would be really nice
Michael L.
·
·
So that it's not defaulted to checking for duplicates across the entire workspace (which is how it currently seems to be set up to do).
Bruno R.
·
·
Absolutely! You can turn off this setting to allow duplicate leads to be pushed to your workspace!
(90 kB)
Michael L.
·
·
Okay thank you! Is there an option at the campaign level? Or is it just at the workspace level?
Bruno R.
·
·
Hi Michael - unfortunately there's no way to duplicate leads at the campaign level as Instantly's API does not allow you to do this, can you clarify what the use case for this would be?
Channeled
APP
·
·