BullhornHub AdvancedInstall

Summary

Update an existing Task record in BullhornHub by specifying its ID and the fields to modify.

Inputs

• Authentication — Choose between User Credentials (Email & Password) or Enterprise Credentials (API Key) for authentication.
• Enable Operations Log — Set to true to emit an audit log row to a secondary output for every write operation, useful for auditing.
• ID (required) — The numeric ID of the Task record to update.
• Input Mode (required) — Select how to provide update data: Field Pairs (build fields in the UI) or JSON Object (supply a JSON payload).
• Data (JSON) — A JSON string representing the fields and values to update on the Task record; empty or null values are skipped. Numeric references auto-wrap as {id: number}.
• Fields — A collection of field name and value pairs specifying which Task fields to update and their new values, used when Input Mode is Field Pairs.
• Output Fields — Fields to include in each output item, merged into results, no-results, and error items.

Output shape

a single updated Task entity record with specified output fields included

The operation succeeds as a no-op if given an empty update payload. An optional Operations Log output is available if enabled, providing audit trail data. Returned data merges requested output fields.

Examples

Example 1: Update Task status and priority by ID

Provide Authentication type, set Task ID, choose Input Mode as Fields, add Fields for 'status' and 'priority' with new values, and specify output fields to return updated values.

Links

• n8n community nodes installation guide