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
Appointment → Update
AI-generatedSummary
Update an existing Appointment record in Bullhorn by specifying its ID and the fields to change, either as individual field-value pairs or as a JSON object containing the update payload.
Inputs
- Authentication (required) — Choose between User Credentials (Email & Password) or Enterprise Credentials (API Key) for authentication.
- Enable Operations Log — Boolean toggle to emit an audit log row to a second output for each write operation for audit trailing.
- ID (required) — The numeric ID of the Appointment record to update.
- Input Mode (required) — Choose how to provide update data: either as Field Pairs (individual fields and values) or as a JSON Object payload.
- Data (JSON) — When Input Mode is JSON Object, provide the update payload as a JSON string; fields with empty, null, or undefined values will be skipped. Numeric TO_ONE references are auto-wrapped.
- Fields — When Input Mode is Field Pairs, specify the Appointment fields and their new values to update. Only include fields to change.
- Output Fields — Fields to include in every output item (merged into results and errors) for downstream use.
Output shape
a single record representing the updated Appointment entity, including requested output fields.
If Enable Operations Log is true, a second output will emit audit log entries for the update operation. Partial updates are supported by including only fields to change. Providing an empty JSON payload will perform a no-op update that succeeds without changes.