BullhornHub AdvancedInstall

Summary

Update a Note record in BullhornHub by its ID with specified field values defined either as individual field pairs or a JSON object.

Inputs

• Authentication — Select authentication method: User Credentials (email & password) or Enterprise Credentials (API Key). Defaults to Enterprise Credentials.
• Enable Operations Log — Optional boolean to emit an audit log row to a secondary output for each write operation, useful for maintaining an audit trail.
• ID (required) — The numeric ID of the Note record to update.
• Input Mode (required) — Choose how to provide data for update: 'Field Pairs (UI)' to specify individual fields and their values in the UI, or 'JSON Object' to provide a raw JSON payload with selective fields to update.
• Fields — When 'Field Pairs (UI)' mode is selected, specify one or more Bullhorn API field names and their new values to update on the Note record.
• Data (JSON) — When 'JSON Object' mode is selected, provide a JSON string representing fields and values to update. Empty, null, or undefined values are skipped. Numeric TO_ONE relationship references are auto-wrapped as {id: value} for proper API formatting.
• Output Fields — Optionally specify fields to include in every output item, merged into results, no-results, and error items for consistent workflow data.

Output shape

a single JSON object representing the updated Note record, optionally enriched with specified output fields, or an error object if the update fails.

The update succeeds as a no-op if the update payload is empty. Numeric TO_ONE relationship fields in the JSON object are automatically wrapped to the API's expected format. If 'Enable Operations Log' is true, an additional output is emitted containing audit log entries for the update operation.

Links

• n8n community nodes installation guide