Short answer: Drop the "HubSpot → Create Ticket" 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 |
|---|---|---|---|
Subject subject | string | Required | Subject. Example: Cannot login to dashboard |
Description content | string | Optional | Description |
Pipeline ID hs_pipeline | string | Optional | Ticket pipeline ID. Leave empty for default. |
Pipeline Stage ID hs_pipeline_stage | string | Optional | Pipeline Stage ID. Example: 1 |
Priority hs_ticket_priority | options | Optional | Priority. Options: Low, Medium, High |
{"subject": "e.g. Cannot login to dashboard","content": "{{trigger.content}}","hs_pipeline": "e.g. 0","hs_pipeline_stage": "e.g. 1","hs_ticket_priority": "{{trigger.hs_ticket_priority}}"}
{"id": "701","properties": {"subject": "Cannot login","hs_pipeline_stage": "1"}}
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.