Home
Events
Groups
Members

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

University
Clay live events

Powered by Tightknit

Delaying SFDC Lookup Enrichment: Workaround for Demo Submission Workflow | Clay

Delaying SFDC Lookup Enrichment: Workaround for Demo Submission Workflow

·

·

Hi is there a way to delay a SFDC lookup enrichment? Or is there a better workaround to what I'm trying to accomplish Here's my workbook. This is the workflow I'm trying to set up

Demo submissions are sent to a Demo table in my Inbounds Workbook via Webhook
A Lookup Record (SFDC) enrichment is run based on the website domain
If no match is found, the company name and its domain are sent to another table in the workbook called New Accounts

New Accounts is a centralized table to create new Account records in SFDC based on a standard set of enrichments

A second Lookup Record (SFDC) enrichment on the Demo table runs when Write to Other Table has run successfully

This is where the workflow is currently breaking

Auto-update executes before the new record is created in New Accounts
Subsequent manual runs of the cell return no results despite a record existing that meet the criteria in SFDC

The second Lookup Record returns some firmographics and the Account owner
Finally, a Slack notification is sent with this information

If there's a better way to handle this, I'm all ears 🙏🏼

4 comments

· Sorted by Oldest

Channeled
APP
·
·
To address your workflow issue, we can use conditional runs and optimize your enrichment process. Here's a suggested approach: 1. Use the "write to table" feature to send data to your New Accounts table. 2. Set up a conditional run for the second SFDC lookup. This ensures it only runs after the new record is created in New Accounts. 3. Use AI formulas to create a custom conditional run. For example: • Click on "Run Settings" then "Conditional Run" • Generate a formula that only runs if the new record exists in the New Accounts table This approach should prevent the auto-update from executing before the new record is created, optimizing your workflow and ensuring you get the most relevant data.
Sources: AI Formulas + Conditional Runs [Clay 101] - Clay University Salesforce [Clay 101] - Clay University AI Formulas + Conditional Runs [CRM Enrichment] - Clay University
Channeled
APP
·
·
Was that helpful?
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!
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 Clay Support.