Short answer: Drop the "HubSpot → Create 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 dealname | string | Required | Deal Name. Example: Enterprise Annual Contract |
Amount amount | string | Optional | Deal value in your account currency |
Deal Stage ID dealstage | string | Optional | The pipeline stage ID. Check your pipeline settings for stage IDs. |
Pipeline ID pipeline | string | Optional | Pipeline to create the deal in. Leave empty for the default pipeline. |
Close Date closedate | string | Optional | Expected close date (ISO 8601 or YYYY-MM-DD) |
Owner ID hubspot_owner_id | string | Optional | HubSpot user ID of the deal owner |
{"dealname": "e.g. Enterprise Annual Contract","amount": "e.g. 10000","dealstage": "e.g. appointmentscheduled","pipeline": "e.g. default","closedate": "e.g. 2025-06-30"}
{"id": "1001","properties": {"amount": "10000","dealname": "Enterprise Annual Contract","dealstage": "appointmentscheduled","createdate": "2025-01-15T12:00:00.000Z"}}
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.