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 updating it according to the update mode or creating a new record if none is found and creation is enabled.
Inputs
- Authentication (required) — Choose BullhornHub User Credentials (email and password) or Enterprise Credentials (API key) for authentication.
- Enable Operations Log — Optionally emit an audit log entry for every write operation to a third output for audit trail purposes.
- Matched Entity ID — Pre-resolved entity ID to skip search and directly update or confirm this record.
- Match Field — Bullhorn Candidate field to search on to find an existing record if no matched entity ID is provided.
- Match Value — Value to search for in the specified match field.
- Update Mode (required) — How to handle updating fields on existing record: only update empty fields, overwrite all fields, or don't update existing records (match only).
- Create If Not Found (required) — Whether to create a new Candidate record if no existing record matches the search criteria.
- Input Mode (required) — Source of field data for the upsert: either from the 'mapped' object output by a BullhornHub Importer node or manual mapping of fields.
- Mapped Data Reference — Expression pointing to the mapped data object when using importer input mode.
- Values to Send — Manually map specific Bullhorn Candidate fields to values for the upsert operation.
Output shape
a list of objects representing the operation result per input item, indicating actions like created, updated (enriched), matched (no update), unchanged, no result found, or ambiguous matches
If a matching Candidate is found and update mode allows, fields are updated per the update mode; if none is found, a new Candidate may be created if enabled. Ambiguous or no matches produce no-result outputs. Operations log entries are emitted if enabled, to a third output. Errors are reported per item if continueOnFail is set.