ActionFreshsalesUpdated September 2026
How do I update a Freshsales deal?
Short answer: You can update freshsales deal in Freshsales by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshsales Update Freshsales Deal action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Deal ID deal_id | string | Required | The numeric ID of the deal to update |
Deal Name name | string | Optional | Deal Name. Example: Enterprise Annual Contract |
Amount amount | string | Optional | Updated deal value |
Expected Close Date expected_close | string | Optional | YYYY-MM-DD format |
Stage ID deal_stage_id | string | Optional | Move the deal to this stage |
Sample request
{"deal_id": "e.g. 12345","name": "e.g. Enterprise Annual Contract","amount": "e.g. 15000","expected_close": "e.g. 2025-09-30","deal_stage_id": "e.g. 3"}
Returns
{"deal": {"id": 12345,"name": "Enterprise Annual Contract","amount": 15000,"deal_stage_id": 3}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Update Freshsales Deal.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Update Freshsales Deal.
What does the Update Freshsales Deal action do in Freshsales?
Updates deal fields — stage, value, owner, expected close date. For "deal moved in external system → reflect in Freshsales" sync workflows.
What inputs does Update Freshsales Deal require?
Required: Deal ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Freshsales returns an error?
The run history shows the failed step with its input and the error message Freshsales returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Update Freshsales Deal support batch operations?
Run Update Freshsales Deal inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Freshsales's rate limits.
More actions
Other Freshsales actions.
Action
Create Freshsales Account
Creates a company/account record. Useful for "new B2B prospect → account record before contact" workflow patterns.
ActionCreate Freshsales Contact
Creates a new contact with email (dedupe), name, custom fields, and optional account association. The base hook for "form submission → push to Freshsales" sync workflows.
ActionCreate Freshsales Deal
Creates a deal with name, amount, pipeline, stage, contact. For "qualified lead → auto-create deal in the AE's pipeline" workflows.
ActionDelete Freshsales Contact
Hard-deletes a contact. For GDPR right-to-erasure workflows; for soft removal use a custom "deleted" tag or status field.
ActionDelete Freshsales Deal
Removes a deal from the pipeline. For "duplicate deal cleanup" or "lost deal archiving" maintenance workflows.
ActionGet Freshsales Contact
Returns a contact by ID with all standard and custom fields plus related deals and activities. The standard lookup before update workflows.