ActionHubSpotUpdated May 2026

How do I delete a HubSpot support ticket?

Short answer: Drop the "HubSpot → Delete 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.

Sample request

{
  "ticket_id": "e.g. 4567890123"
}

Returns

{
  "success": true
}

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

Triggered by

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

What does the Delete Ticket action do in HubSpot?

Deletes a HubSpot support ticket by ID. Archived tickets are recoverable from the recycle bin for 90 days.

What inputs does Delete 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 Delete Ticket support batch operations?

Yes. Run Delete 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