Actions35
- Contact Actions
- Contact Property Actions
- Deal Actions
- Event Actions
- Note Actions
- Pipeline Actions
- Segment Actions
- Tag Actions
- Task Actions
Deal → Update
AI-generatedSummary
Updates an existing SwipeOne deal, optionally moving it to another pipeline or stage and changing its name, value, owner, priority, or expected close date. The source pack only shows signatures, so the exact request and return shape are not visible.
Inputs
- dealId (required) — The deal to update. Choose from a searchable list of deals or enter the deal ID directly (e.g. 507f1f77bcf86cd799439011).
- pipelineId — Pipeline to move the deal to. Options are loaded from the workspace's pipelines. Selecting one also determines which stages are offered.
- stageId — Stage to move the deal to. Options depend on the selected pipeline. An ID can also be given via expression.
- updateFields — Collection of optional fields to change: Expected Close Date (date/time), Name (string), Owner (workspace user), Priority (None=0, Low=1, Medium=2, High=3), and Value (number, the deal's monetary value).
Output shape
Most likely the updated deal record for each input item, though the source is not visible to confirm this.
The execute function body is not included in the source pack, so the return shape is unverified. Errors from the SwipeOne API will probably surface as node errors.
Examples
Example 1: Advance a deal to the next stage when a contract is signed.
Set Deal by ID from an earlier node, choose the Pipeline and a 'Closed Won' Stage.
Example 2: Reassign a deal and raise its priority.
Set Deal, then in Update Fields add Owner and set Priority to High.
Example 3: Update a deal's value and expected close date after a negotiation.
Set Deal, then in Update Fields set Value and Expected Close Date.