ActionHubSpotUpdated June 2026

How do I update a HubSpot support ticket?

Short answer: Drop the "HubSpot → Update Ticket" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 23 HubSpot actions

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
Ticket ID ticket_id	string	Required	HubSpot ticket record ID — a numeric string. Find via List Tickets.
Subject subject	string	Optional	Message subject line.
Content content	string	Optional	Content
Pipeline Stage hs_pipeline_stage	string	Optional	Pipeline Stage. Example: 1 (New), 2 (Waiting), 3 (Closed)
Priority hs_ticket_priority	options	Optional	Priority. Options: Low, Medium, High

Sample request

{
  "ticket_id": "e.g. 4567890123",
  "subject": "e.g. Quick update",
  "content": "{{trigger.content}}",
  "hs_pipeline_stage": "e.g. 1 (New), 2 (Waiting), 3 (Closed)",
  "hs_ticket_priority": "{{trigger.hs_ticket_priority}}"
}

Returns

{
  "id": "123456",
  "properties": {
    "subject": "Updated subject",
    "hs_pipeline_stage": "3"
  }
}

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

Triggered by

Apps that pair well as the trigger for Update 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 Update Ticket.

What does the Update Ticket action do in HubSpot?

Updates a HubSpot support ticket: pipeline stage, priority, owner, or custom properties. The standard hook to reflect downstream actions back into HubSpot.

What inputs does Update Ticket require?

Required: Ticket ID. 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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Update Ticket support batch operations?

Yes. Run Update Ticket inside a Loop node to process arrays. Tiny Command handles HubSpot's rate limits automatically so you don't have to throttle manually.

More actions