Delaying Salesforce Enrichment: Seeking Effective Strategies | Clay

Delaying Salesforce Enrichment: Seeking Effective Strategies

Has anyone had success with a method to delay a Salesforce enrichment (or any enrichment field)? I have a table that creates leads → sends them to another table → performs a lookup on the Lead ID. But I need to delay the second lookup because the object hasn’t yet been enriched with the Outreach ID and other data I need for the next step. I’ve tried a few formula fields that check the created timestamp and wait 5 minutes, but no luck—since the formula is only evaluated when the input field changes. I know I could run webhooks from Zapier with a delay, but I’d like to avoid that since this seems like a fairly simple function, and adding Zapier would increase complexity and reduce reliability. Any feedback or ideas would be appreciated!

7 comments

Channeled
APP
·
·
Unfortunately, we don't currently have a built-in feature to delay enrichments or lookups within Clay. Scheduling enrichments is a feature we're actively working on, but it's not available yet. In the meantime, you might consider using our CRM sync feature. If you're using a table with a CRM source, it'll update in a two-way sync every 24 hours. This could potentially help with your Salesforce enrichment delay issue. Is there a specific reason you need to delay the enrichment? Understanding your use case better might help us suggest alternative approaches within Clay's current capabilities.
Sources: FAQ | Clay.com Can I schedule data enrichments so they re-run on their own? - FAQ | Clay.com
Alek J.
·
·
Because when leads get created I need to wait for all the lead information to populate in SF.
Channeled
APP
·
·
Unfortunately, we don't currently have a built-in feature to delay enrichments or lookups in Clay until Salesforce data is fully populated. However, here are some strategies you can try: 1. Use conditional runs to qualify leads early in your workflow. 2. Consider using our CRM sync feature, which updates every 24 hours for tables with a CRM source. 3. Implement a "Last Enrichment Date" field in your Clay table and use it to trigger updates only after a certain time has passed. If these solutions don't meet your needs, you may need to request human assistance for a more tailored approach.
Sources: Salesforce integration overview | Documentation | Clay University Salesforce Integration Guide Keeping your CRM Up to Date With Clay [CRM Enrichment] - Clay University
Jani V.
·
·
I don't think you can avoid the zapier/make/n8n complexity for this use case
Channeled
APP
·
·
Unfortunately, we don't currently have a built-in feature to delay enrichments or lookups until Salesforce data is fully populated. However, here are some strategies you can try: 1. Use conditional runs to qualify leads early in your workflow. 2. Implement a "Last Enrichment Date" field in your Clay table and use it to trigger updates only after a certain time has passed. 3. Consider using our CRM sync feature, which updates every 24 hours for tables with a CRM source. If these solutions don't meet your needs, you may need to request human assistance for a more tailored approach. Click on "Talk to a person" for further help.
Sources: Salesforce integration overview | Documentation | Clay University Salesforce Integration Guide Keeping your CRM Up to Date With Clay [CRM Enrichment] - Clay University
Channeled
APP
·
·
Alek J.
·
·
Jani V. Thanks, I've been banging my head against the wall for a few hours now trying to thing through this, but I'll likely take the Zapier route for now. Hopefully I can simplify once the scheduling runs becomes available.