Sourcier AdvancedInstall

Summary

Update a Lead record in Bullhorn by specifying its ID and the fields to change, either via individual field-value pairs or a JSON object payload.

Inputs

• Authentication — Select authentication method: User Credentials (Email & Password) or Enterprise Credentials (API Key). Defaults to Enterprise.
• Enable Operations Log — Optionally enable a second output for audit logs on each write operation.
• ID (required) — The numeric ID of the Lead record to update.
• Input Mode — Choose to input fields as individual pairs or as a JSON object payload.
• Data (JSON) — A JSON string representing the fields and values to update; numeric references are auto-wrapped. Empty or null values are skipped. Used if Input Mode is JSON.
• Fields — A collection of individual Bullhorn fields and their new values to update. Used if Input Mode is Field Pairs.
• Output Fields — Fields to include in every output item, merged into results and error objects.

Output shape

a single updated Lead entity response object containing at least the changed entity ID

The operation accepts either a structured JSON payload or individual fields to update. If the update payload is empty, the operation completes successfully as a no-op. Enabling Operations Log adds a second output with audit log records.

Examples

Example 1: Update a Lead with specific fields

Set Authentication to Enterprise Credentials, specify ID as 12345, Input Mode as Field Pairs, and add field updates like status:'Active', priority:'High'. Disable Operations Log unless audit trail is needed.

Example 2: Update a Lead using a JSON object

Set Authentication to User Credentials, specify ID as 67890, Input Mode as JSON, and provide a JSON string such as '{"status":"Inactive","owner":456}'. Enable Operations Log for audit purposes if desired.

Links

• n8n community nodes installation guide