BullhornHub Matcher
AI-generatedSummary
Match a Bullhorn entity record by performing a prioritized multi-field search using identifiers such as LinkedIn URL, domain, email, name, and location data with confidence scoring and optional audit logging.
Inputs
- authentication — Select BullhornHub User Credentials or Enterprise Credentials for API authentication.
- enableOperationsLog — Enable to emit an audit log entry for each match attempt to a third output for tracking matched, ambiguous, and not found attempts.
- entity (required) — Specify the Bullhorn entity type to match against: Company (ClientCorporation), Contact (ClientContact), or Candidate.
- linkedInUrl — Source LinkedIn URL to match (highest priority, confidence 100). Leave empty to skip.
- domain — Company domain for matching (priority 2, confidence 90). Only for ClientCorporation; skipped if domain is in generic domain blacklist.
- email — Email address for matching (priority 2, confidence 95). Used for Contact and Candidate entities only.
- name — Company name for matching (priority 3-5). Used with ClientCorporation entity; leave empty to skip name-based matching.
- firstName — First name for matching (priority 3). Used with Contact and Candidate entities.
- lastName — Last name for matching (priority 3). Used with Contact and Candidate entities.
- city — City for disambiguation with company name (optional). Used for ClientCorporation only.
- options.genericDomains — List of generic domains to exclude from domain matching to avoid false positives.
- options.autoMatchThreshold — Minimum confidence score (0-100) to automatically accept a match; matches below this are sent to the Not Matched output.
- options.fuzzyThreshold — Similarity ratio (0-1) needed to accept a fuzzy name match at priority 5.
- options.matchFields — Comma-separated list of Bullhorn fields to return in the match result; defaults to entity-specific fields if empty.
- options.maxCandidates — Maximum number of candidates to consider per matching strategy before declaring ambiguous.
Output shape
Two or three outputs with arrays of matching results. The first output emits matched records, the second emits not matched or ambiguous records, and the optional third emits operations log entries when enabled.
The node returns on its first output matched records meeting or exceeding the confidence threshold. Records below that threshold or ambiguous matches go to the second output. If 'Enable Operations Log' is on, audit log entries for each attempt are emitted to a third output. Each match result includes match details such as confidence, strategy used, matched record data, and source input.
Examples
Example 1: Match a company record using LinkedIn URL and domain with enterprise credentials.
Set Authentication to 'BHH Enterprise Credentials', Entity to 'ClientCorporation', provide LinkedIn URL and Domain, optionally with Company Name and City, and set 'Enable Operations Log' to true to track match attempts.