Actions206
- Accessory Actions
- Actual Content Actions
- Alternative Actions
- Appointment Actions
- Appointment Crew Actions
- Contact Actions
- Contact Person Actions
- Contract Actions
- Cost Actions
- Crew Actions
- Crew Availability Actions
- Crew Rate Actions
- Equipment Actions
- Equipment Assigned Serial Actions
- Equipment Sets Content Actions
- Extra Input Field Actions
- Factor Actions
- Factor Group Actions
- File Actions
- File Folder Actions
- Folder Actions
- Invitation Actions
- Invoice Actions
- Invoice Line Actions
- Leave Mutation Actions
- Leave Request Actions
- Leave Type Actions
- Ledger Code Actions
- Payment Actions
- Project Actions
- Project Crew Actions
- Project Equipment Actions
- Project Equipment Group Actions
- Project Function Actions
- Project Function Group Actions
- Project Request Actions
- Project Request Equipment Actions
- Project Type Actions
- Project Vehicle Actions
- Purchase Order Actions
- Purchase Order Cost Actions
- Purchase Order Global Cost Actions
- Quote Actions
- Rate Actions
- Rate Factor Actions
- Repair Actions
- Serial Number Actions
- Status Actions
- Stock Location Actions
- Stock Movement Actions
- Sub Rental Actions
- Sub Rental Equipment Actions
- Sub Rental Equipment Group Actions
- Subproject Actions
- Subtask Actions
- Supplier Actions
- Task Actions
- Task Assignment Actions
- Task Status Actions
- Tax Class Actions
- Time Registration Actions
- Time Registration Activity Actions
- Vehicle Actions
Task → Update
AI-generatedSummary
Updates an existing Rentman task by ID, sending only the fields you add under Additional Fields in the request body to the Rentman API (/tasks/{id}).
Inputs
- taskId (required) — ID of the task to update; used in the request URL /tasks/{id}.
- additionalFields — Collection of optional fields to change. Only the fields you add are sent. Options: name, details, assignment_type (all crew, creator only, selected crew), priority, status (path such as /taskstatuses/0), public (private/public), is_template, time_budget, order, completed_at, completed_by (crew path such as /crew/0), item (numeric ID) and itemtype (Project, Contact, Crew, Equipment, Invoice, Quote, Vehicle and others), deadline, deadline_type (specific date or relative to project time), relative deadline offset amount/unit/base/direction, expiry_notification_date, recurrence settings (recurhoe, recurperiode, recureind), synchronization_id and synchronization_uri. Empty date values are sent as null, and an item of 0 or less is omitted.
- requestOptions — Node settings for HTTP behavior: batching (items per batch, interval in ms), ignore SSL issues, proxy, and timeout (default 10000 ms).
Output shape
The updated task record as returned by the Rentman API for the request.
The source pack contains only compiled stubs, so the response shape is not confirmed in the source. This is a declarative routing node and the response is presumably passed through as returned by the API. Clearing a date field by leaving it empty sends null.
Examples
Example 1: Mark a task as high priority and update its description
Task ID = 123; Additional Fields: Priority = High, Details = 'Confirm truck loading before 8am'.
Example 2: Complete a task and record who finished it
Task ID = 123; Additional Fields: Completed At = a date/time, Completed By (Path) = /crew/42, Status (Path) = /taskstatuses/3.
Example 3: Set a deadline relative to the project start
Task ID = 123; Additional Fields: Deadline Type = Relative to Project Time, Offset Amount = 2, Unit = Days, Direction = Before, Base = Start of Period.