ActionHubSpotUpdated September 2026

How do I create a HubSpot support ticket?

Short answer: You can create ticket in HubSpot by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the HubSpot Create Ticket 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.

Create Ticket in HubSpot — start free All 23 HubSpot actions

Create Ticket in HubSpot — start free

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
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

Sample request

{
  "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}}"
}

Returns

{
  "id": "701",
  "properties": {
    "subject": "Cannot login",
    "hs_pipeline_stage": "1"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create Ticket.

Any of these apps can fire this action as part of a workflow.

Google Sheets → HubSpot

2 Google Sheets triggers

Stripe → HubSpot

10 Stripe triggers

FAQ

Questions about Create Ticket.

What does the Create Ticket action do in HubSpot?

Creates a support ticket in HubSpot with subject, content, pipeline, stage, priority, owner, and associated contact/company. The default write for converting external alerts into tracked tickets.

What inputs does Create Ticket require?

Required: Subject. 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 HubSpot returns an error?

The run history shows the failed step with its input and the error message HubSpot 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 Create Ticket support batch operations?

Run Create Ticket 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 HubSpot's rate limits.

More actions