Sourcier MatcherInstall

Summary

Match input data against Bullhorn entities using a cascading multi-field search with confidence scoring and return matched or not matched results, optionally logging operations.

Inputs

• authentication (required) — Select authentication method: BHH User Credentials or BHH Enterprise Credentials.
• enableOperationsLog — Toggle to emit an audit log row to a third Operations Log output for every match attempt.
• entity (required) — Specify which Bullhorn entity type to match against: Company (ClientCorporation), Contact (ClientContact), or Candidate.
• linkedInUrl — Source LinkedIn URL used for Priority 1 (confidence 100) matching. Leave empty to skip.
• domain — Source company domain used for Priority 2 (confidence 90) matching, skipped if in generic domain blacklist. Applicable only for ClientCorporation. Leave empty to skip.
• email — Source email used for Priority 2 (confidence 95) matching, unique identifier for contacts/candidates. Leave empty to skip.
• name — Source company name used for Priority 3-5 matching. Applicable only for ClientCorporation. Leave empty to skip.
• firstName — Source first name for Priority 3 matching, applicable for contacts and candidates.
• lastName — Source last name for Priority 3 matching, applicable for contacts and candidates.
• city — Source city used for name disambiguation (optional) in Priority 3 for ClientCorporation.
• options.genericDomains — List of domains to skip for Priority 2 domain matching to avoid false positives due to common platform domains.
• options.autoMatchThreshold — Minimum confidence score (0-100) required to accept a match as valid; matches below this threshold are output as not matched.
• options.fuzzyThreshold — Similarity ratio (0-1) threshold to accept a fuzzy name match at Priority 5, default is 0.85 (85%).
• options.matchFields — Comma-separated Bullhorn fields to return in the match result; defaults are used if empty.
• options.maxCandidates — Maximum number of candidate results to consider per strategy before declaring ambiguous.

Output shape

multiple outputs: main matched results array on first output, not matched results array on second output, and optionally operations log array on third output if enabled.

Matched output items include matched status, entity ID and type, confidence score, match strategy used, the matched Bullhorn record, and source input. Not matched output items include matched status false, confidence, ambiguity flag, reason, and source input data. Operations Log output, if enabled, emits audit records for each match attempt, including timestamps, entity info, action, and confidence. Pagination is controlled internally by maxCandidates option. Errors per item can pass through if node is set to continue on fail.

Links

• n8n community nodes installation guide