Upsert
AI-generatedSummary
Upsert a Bullhorn Candidate record by searching for an existing record using a matched entity ID or a specified match field and value, then either updating it according to the selected update mode or creating a new record if none is found.
Inputs
- Authentication (required) — Choose between User Credentials (Email & Password) or Enterprise Credentials (API Key) for authentication.
- Enable Operations Log — Toggle to emit an audit log record for each write operation.
- Matched Entity ID — Use a pre-resolved Bullhorn entity ID to skip searching for a match.
- Match Field — Bullhorn field to search on if Matched Entity ID is not provided.
- Match Value — Value to match in the specified field; required if no Matched Entity ID is provided.
- Update Mode (required) — Define how to update matched records: only empty fields, overwrite all fields, or perform no update.
- Create If Not Found (required) — Whether to create a new Candidate record if no existing match is found.
- Input Mode (required) — Select whether to get field data from a Sourcier Importer node's mapped output or map fields manually.
- Mapped Data Reference — Expression to retrieve the mapped field data when input mode is 'importer'. Defaults to reading $json.mapped.
- Values to Send — Manually map Bullhorn Candidate fields to values for the upsert operation when using manual mapping.
Output shape
a list of JSON objects representing the upsert results and optionally an operations log output if enabled.
Outputs two JSON array outputs by default: one with results for successful upsert attempts or matches, and one with no-result or error information. A third "Operations Log" output is added if 'Enable Operations Log' is true. Each record indicates the action taken (created, updated, enriched, matched, unchanged, not_found, ambiguous) and relevant metadata such as entity ID, changes made, and source data.