Outcome. New contacts with a business email get linked to the matching company record automatically, instead of sitting unassociated until a rep notices and fixes it by hand.
Workflow map
Enrollment, branches and actions at a glance
data-quality-006
flowchart TD
A[Contact email known, no company yet] --> B[Custom code: extract domain, skip free-mail, search Companies API]
B --> C{Result count}
C -->|0| D[Status: No match found]
C -->|1| E[Create association via API]
E --> F[Status: Matched]
C -->|2+| G[Status: Multiple matches - manual review]
G --> H[Add to review list + create task]
When to use it, when not to
- UseUse it when contacts commonly arrive without a company association: web forms, chat, imports, or manual creation by reps who skip the company field.
- UseUse it when the company database is already reasonably populated
with a clean
domainvalue, since the match depends on that field. - SkipDo not use it on a portal where most contacts use free-mail addresses (gmail.com, outlook.com, and similar). Domain matching cannot work there; route those contacts to manual review instead.
- SkipDo not use it expecting it to create new company records. This workflow only links to a company that already exists. See data-quality-009 for enforcing company data at creation, and the Variants section for a paired approach.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.5 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.7 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the data quality pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
