BullhornHub Contact icon

BullhornHub Contact

Manage Bullhorn contacts — CRUD, notes, parent company

Actions10

Upsert

AI-generated

Summary

Upsert a BullhornHub Contact by searching for an existing record via a Matched Entity ID or a field/value pair, then update fields according to an update mode or create a new contact if none is found and creation is enabled.

Inputs

  • Authentication (required) — Select either User Credentials (Email & Password) or Enterprise Credentials (API Key) for BullhornHub authentication.
  • Matched Entity ID — Provide a pre-resolved BullhornHub Contact ID to skip search and upsert directly on this ID.
  • Match Field — Bullhorn field name to search by when looking for existing contacts, ignored if Matched Entity ID is given.
  • Match Value — Value to search in the match field for existing contacts, ignored if Matched Entity ID is given.
  • Update Mode (required) — Choose how to update fields on an existing contact: update only empty fields, overwrite all, or don't update existing records (match only).
  • Create If Not Found (required) — Boolean flag to create a new contact if no matching contact is found.
  • Input Mode (required) — Select whether to take input data from a BullhornHub Importer node's mapped data or manually map fields.
  • Mapped Data Reference — Expression returning the mapped data object when using Input Mode 'From BHH Importer'; defaults to $json.mapped.
  • Values to Send — Manually map Bullhorn Contact fields to values for the upsert operation when Input Mode is 'Manual Mapping'.

Output shape

a list of results objects representing the upsert outcome for each input item, including created or matched entity IDs and update actions; plus a list for no-results scenarios; optionally a third audit log list if operations logging is enabled

The operation either uses a pre-resolved entity ID or searches using Match Field and Match Value. If multiple matches occur, the upsert skips updates to avoid data contamination. Update Mode controls whether existing non-empty fields are preserved or overwritten. When no match is found and creation is enabled, a new contact record is created. Field data can be sourced from upstream BullhornHub Importer output or manual field mappings. If Enable Operations Log is on, audit log entries are emitted as a third output.

Links

Discussion