BullhornHub AdvancedInstall

Summary

Update an existing Sendout record in Bullhorn by specifying its ID and the fields to modify, using either UI field pairs or a JSON object for the update payload.

Inputs

• Authentication (required) — Choose between User Credentials (Email & Password) or Enterprise Credentials (API Key) for authentication.
• Enable Operations Log — Optionally emit an audit log entry to a secondary output for each write operation to help maintain an audit trail.
• ID (required) — The unique ID of the Sendout record to update.
• Input Mode (required) — Method to build the update payload: either as individual field-value pairs or a JSON object.
• Fields — Provide the Bullhorn fields and their new values as field pairs when using the 'fields' input mode.
• Data (JSON) — Provide a JSON object with the fields to update when using the 'json' input mode; empty, null, or undefined values are skipped and TO_ONE references are automatically wrapped.
• Output Fields — Specify additional fields to include in each output item, merged with results and error items.

Output shape

a single record containing the updated Sendout entity fields as returned from the Bullhorn API

Only the specified fields are updated; using an empty JSON payload performs a no-op but returns success. The operation supports conditional logging to an additional output for audit trail purposes.

Examples

Example 1: Update Sendout status and date using field pairs

Authentication set to 'Enterprise Credentials', ID set to the Sendout to update, Input Mode 'fields' selected with status and date fields provided.

Example 2: Update Sendout using pre-built JSON object

Authentication set to 'User Credentials', ID set, Input Mode 'json' with a JSON payload specifying fields and values to update.

Links

• n8n community nodes installation guide