Consider checking records via the Lookup records action early on in your workflow
Given that calling on Salesforce actions won’t cost you any credits, you should make the most out of this. Here are a few scenarios where you should run the Lookup records action:
Checking Salesforce to make sure the lead you pulled isn’t a duplicate
Pulling in your CRM company data from Salesforce of a lead list you brought in
Making sure your outbound table contacts are not on an exclusion or suppression list
Qualify or filter leads early on via conditional runs so you can spend credits enriching the right leads
In most cases, not all the leads you import into your Clay table are qualified. Qualifying leads early on in your Clay workflow can help you save many credits. You can often qualify leas with just the data from Enrich Company or Enrich People actions, which are free.
Understand the relationships of between your contact and company records
Every CRM is structured differently, so we can’t prescribe a one-size-fits all approach on when to Lookup records, Update records, or Create records. However, understanding the relationships of your contacts and mapping this out explicitly can help you understand when and where you should run Salesforce actions.
Here are a few key questions to consider:
For contacts:
What do I do with contacts that have a company? What if they don’t have a company?
If a contact does not have a company tagged to them, what rules do you assign to these contacts?
How do you resolve multiple companies tied to the same one contact? How do you resolve a case where one company has many variations of one contact?
For companies: What do I do with companies that have no contacts?
Answering these questions can inform questions like which property to treat as the source of truth, which will help you then know which action to run.