Create Ticket
hubspot.create_ticket
ActionCRM & salesconnection required
Calls the HubSpot API with the connection's credentials.
Create a support ticket with POST /crm/v3/objects/tickets. HubSpot requires a subject and a pipeline stage id; read the ids with hubspot.list_pipeline_stages for object type tickets.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- HubSpot
- Secret shape
- the HubSpot private-app token, or {"token": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
8 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
subject The ticket's name, shown as its title in HubSpot. | string | Yes | — | — | Login fails after password reset |
hs_pipeline_stage Id of the status the ticket opens in — the internal stage id, never its label. Read the ids with hubspot.list_pipeline_stages. | string | Yes | — | — | 1 |
hs_pipeline Id of the ticket pipeline. Required when the portal has more than one. | string | No | — | — | — |
content The ticket's description. | string | No | — | — | — |
hs_ticket_priority The ticket's priority. | string | No | — | one of "LOW", "MEDIUM", "HIGH" | — |
hubspot_owner_id Id of the owner the ticket is assigned to; read the ids with hubspot.list_owners. | string | No | — | — | — |
properties Properties to set, as a JSON object keyed by HubSpot's internal property name. | object | No | — | — | — |
associations Records to associate as the record is created, as HubSpot's JSON array of {"to": {"id": "…"}, "types": [{"associationCategory": "HUBSPOT_DEFINED", "associationTypeId": 1}]} objects. | array | No | — | array of object | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"hs_pipeline_stage": "1",
"subject": "Login fails after password reset"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The record's HubSpot object id. | string | — |
properties The record's properties, keyed by HubSpot property name. | object | — |
createdAt When the record was created, ISO 8601 UTC. | string | — |
updatedAt When the record was last modified, ISO 8601 UTC. | string | — |
archived True when the record sits in the recycling bin. | boolean | — |
{
"archived": false,
"createdAt": "",
"id": "",
"properties": {},
"updatedAt": ""
}See Create Ticket run in a workflow.
In a technical demo we add the HubSpot connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.