BullhornHub AdvancedInstall

Summary

Update an existing Contact record in BullhornHub using specified field values or a JSON object payload.

Inputs

• Authentication — Choose between User Credentials (email and password) or Enterprise Credentials (API key) for authentication.
• Enable Operations Log — Optionally enable an audit log output for the update operation for tracking purposes.
• ID (required) — The numeric ID of the Contact record to update.
• Input Mode — Select how to provide update data: either via individual field-value pairs or a JSON object payload.
• Data (JSON) — A JSON string representing the fields and values to update selectively when Input Mode is 'JSON Object'. Empty or null values are skipped. Numeric TO_ONE references (e.g., {"clientCorporation": 123}) are automatically wrapped as {id: 123}.
• Fields — A collection of Bullhorn field/value pairs to update individually when Input Mode is 'Field Pairs (UI)'. Only include fields you want to change.
• Output Fields — Specify additional fields to include in every output item, merged into results or errors for better context.

Output shape

a single record representing the updated Contact entity.

The update operation succeeds even with an empty payload, effectively causing no changes. If 'Enable Operations Log' is enabled, an additional audit log record is emitted on a second output. Numeric TO_ONE references in JSON are automatically handled. Only the fields specified in the input are updated.

Examples

Example 1: Update Contact using field pairs

Set ID to target contact's ID, set Input Mode to 'Field Pairs', then provide field-value pairs such as status = 'Active'. Enable Operations Log optionally.

Example 2: Update Contact using JSON payload

Set ID to contact's ID, set Input Mode to 'JSON Object', supply a JSON string with desired fields and values to update, e.g., {"email": "newemail@example.com"}. Enable Operations Log optionally.

Links

• n8n community nodes installation guide