BullhornHub AdvancedInstall

Summary

Updates a Bullhorn Candidate record by ID using either a field/value map or a JSON payload.

Inputs

• authentication — Authentication method: User Credentials (Email & Password) or Enterprise Credentials (API Key).
• enableOperationsLog — Whether to emit an audit log row to a second 'Operations Log' output for every write operation.
• id (required) — The ID of the Candidate record to update.
• inputMode — How to build the update payload: 'fields' for field/value pairs or '' for a pre-built JSON object.
• updateData — Bullhorn fields and values to update. Only include fields you want to change.
• dataJson — JSON object of fields to write. Empty string, null, and undefined values are skipped — perfect for selective enrichment workflows.
• outputFields — Fields to include in every output item. Merged into results, no-results, and error items.

Output shape

A single record representing the updated Candidate entity.

For update with an empty payload, the operation succeeds as a no-op. TO_ONE references (e.g., {"clientCorporation": 123}) are auto-wrapped as {id: 123}.

Examples

Example 1: Update a Candidate's status using field/value pairs

Set ID to 12345, inputMode to 'fields', and add 'status' and 'statusDate' fields.

Example 2: Update multiple fields using a JSON payload

Set ID to 12345, inputMode to '', and provide a JSON object like {"status":"Available","statusDate":"2024-01-01"}.

Example 3: Perform a no-op update (successful but no changes)

Set ID to an existing Candidate ID and provide an empty payload or JSON string.

Links

• n8n community nodes installation guide