Short answer: Drop the "Freshsales → Create Freshsales Deal" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Deal Name name | string | Required | Name of the deal |
Amount amount | string | Required | Deal value in your account currency |
Contact ID contacts_id | string | Optional | ID of the primary contact for this deal |
Expected Close Date expected_close | string | Optional | Expected close date in YYYY-MM-DD format |
Pipeline ID deal_pipeline_id | string | Optional | ID of the sales pipeline |
Stage ID deal_stage_id | string | Optional | ID of the deal stage within the pipeline |
{"name": "e.g. Enterprise Annual Contract","amount": "e.g. 10000","contacts_id": "e.g. 12345","expected_close": "e.g. 2025-06-30","deal_pipeline_id": "e.g. 1"}
{"deal": {"id": 1,"name": "Enterprise Annual Contract","amount": 10000,"expected_close": "2025-06-30"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.