Actions87
- Appointment Actions
- Candidate Actions
- Company Actions
- Contact Actions
- File Actions
- Job Actions
- Job Submission Actions
- Lead Actions
- Note Actions
- Opportunity Actions
- Placement Actions
- Sendout Actions
- Task Actions
- Tearsheet Actions
Task → Update
AI-generatedSummary
Update a Task entity in Bullhorn by specifying its ID and the fields to modify, either using individual field-value pairs or a JSON payload, with optional audit logging.
Inputs
- Authentication (required) — Choose between User Credentials (Email & Password) or Enterprise Credentials (API Key).
- Enable Operations Log — Toggle to emit an audit log row for this update operation to a second output for audit trail purposes.
- ID (required) — The unique numeric ID of the Task record to update.
- Input Mode (required) — Select how to provide update data: either as individual field-value pairs in the UI or as a JSON object payload.
- Data (JSON) — A JSON object representing the fields and values to update selectively, skipping any empty/null/undefined fields. Numeric TO_ONE references are automatically wrapped in an object with an 'id' property.
- Fields — One or more Bullhorn API fields and their new values to update; only include fields you intend to change when using Field Pairs input mode.
- Output Fields — Specify additional fields to include in the output items merged with the update results.
Output shape
a single record containing the update response from Bullhorn, including the changed entity ID, merged with any specified output fields; optionally, a second output emits audit log entries if enabled.
If the input payload is empty, the operation succeeds as a no-op without changes. The second output is only present when 'Enable Operations Log' is turned on in the node configuration.