Actions74
- Client Actions
- Contact Actions
- Contract Actions
- Estimate Actions
- Expense Actions
- Invoice Actions
- Lead Actions
- Message Actions
- Note Actions
- Payment Actions
- Project Actions
- Proposal Actions
- Task Actions
- Ticket Actions
- User Actions
Contract → Update
AI-generatedSummary
Update a contract with optional fields and optional binary file upload
Inputs
- id (required) — Unique identifier of the contract to update
- sendBinaryData — Whether to include a binary file in the request
- binaryPropertyName (required) — Name of the binary property in the payload that holds the file to upload (used when sendBinaryData is true)
- additionalFields — Object containing optional contract update fields such as client_id, contract_date, title, status, tax_id, discount_amount, etc.
Output shape
array of updated contract records (one per processed item)
Each element corresponds to an input item; may include error objects when continueOnFail is enabled; no pagination for update operations
Examples
Example 1: Mark a contract as sent and attach a file
Set operation to Update, provide contract ID, enable Send Binary Data, set Binary Property to 'data', add Additional Fields with status='sent' and title='Q3 Agreement'
Example 2: Update contract dates and status without file
Set operation to Update, provide contract ID, add Additional Fields with contract_date='2024-01-01', valid_until='2025-01-01', status='draft'