Before
A user would likely search the CRM for contacts by first and last name, review several possible matches, and open each record to inspect its associated company. They would then compare the company domain or name manually before copying the correct contact ID or reporting that no match was found.
How it works
- Receive person and company details, then search for up to four contacts matching the first and last name.
- Validate each candidate against its associated company by comparing the domain first, followed by exact and approximate company-name checks when needed.
- Return the matched contact ID and an existing-contact status, or explicitly return that no contact was found.
Workflow details
- Candidate search: The workflow receives a person's first name, last name, company name, and company domain through a webhook, then searches the CRM for contacts matching the first and last name. It evaluates up to four returned contact candidates sequentially.
- Company validation: For each candidate, the workflow looks up the company associated with that contact and checks whether the supplied company domain matches the associated company's domain, using case-insensitive comparison.
- Name-based fallback: If a usable company domain is not available or the domain does not match, the workflow compares the supplied company name with the associated company name. It first checks for a case-insensitive exact match and then uses an AI-assisted similarity check for names that may be equivalent despite formatting or wording differences.
- Result delivery: When the company validation succeeds, the candidate contact ID is stored and returned in a JSON response with an "Already Exist" status. If no candidate passes the checks, the workflow returns a "No contact found" status with an empty contact ID.
What changed
Contact identification now happens through a single webhook request with automated candidate screening and company validation. The requester receives a consistent JSON result containing either the verified contact ID or an explicit no-match response, while human review is no longer required for the defined checks.
Work removed
Searching contact records one by one, reviewing up to four candidate matches, opening associated company details, comparing company domains and names, checking approximate name variations, copying the matched contact ID, and manually reporting unsuccessful searches.
Expected outcome
Each request can automatically evaluate up to four candidate contacts and return a standardized match or no-match result without the recurring manual comparison steps.
