Enrich contacts before a campaign goes out — Lusha in Salesforce Agentforce

Run it on every campaign that sends to contacts you haven’t verified in the last 30 days. If you’re running the scheduled account enrichment from Workflow 5 weekly, contacts enriched recently may not need re-verification before a campaign — add an entry condition that checks whether Lusha_Last_Verified__c is older than 30 days for each member and skips the API call for recently verified contacts. This reduces credit consumption significantly for teams running frequent campaigns against a well-maintained contact database.

Suppressed contacts remain in the Campaign Member list with a status of “Suppressed — Departed” — they’re excluded from the send but preserved in the campaign record for reporting. This is intentional: the suppression count is useful data for understanding list quality and decay rates over time. If you want to find replacement contacts for suppressed campaign members — particularly for named account campaigns where coverage matters — run the Enrich Contact Skill or the Buying Group play on the accounts where contacts were suppressed.

Salesforce Flow processes HTTP callouts sequentially — one API call per campaign member. At roughly one to two seconds per callout, a campaign list of 500 contacts takes approximately 8 to 15 minutes to verify. For very large campaigns of 2,000+ contacts, consider triggering the verification workflow 24 hours before the planned send date rather than at the “Ready to Send” status change — this gives the Flow enough time to complete before the campaign manager needs to review the suppression report and approve the send.

Yes — the verification logic is the same regardless of the sending tool. The trigger condition needs to change based on how you indicate a list is ready in your workflow, but the core Flow — query campaign members, call Lusha for each one, suppress departed contacts, update stale data — applies equally. If your team uses Marketing Cloud or Pardot rather than Salesforce Campaigns natively, the verification pass can be triggered from a data extension update or a Pardot list status change using a connected Flow or API webhook.

“Not found” means Lusha couldn’t match the contact to a verified record — this happens most often with personal email addresses, contacts at very small companies with limited Lusha coverage, or contacts where the name and email combination doesn’t resolve to a unique match. For these contacts, the safest approach is to include them in the send but flag them for manual review after the campaign — if the email bounces, suppress and remove. If it delivers and gets a reply, the contact is reachable and the record can be manually updated. For high-value named account campaigns where every contact matters, run a manual lookup in Lusha Workspace on the unresolved contacts before the send.