Helpdesk tickets

The Helpdesk node, under Post Processing, opens a ticket when the call ends. Choose where tickets go with Where to file tickets:

Provider	Where tickets go	What it needs
HubSpot Tickets	Your HubSpot Tickets pipeline, linked to the caller’s contact when their email is known	A HubSpot token with ticket write scope, entered under HubSpot in Settings. See Keys.
This dashboard	The Tickets tab of this workspace’s Dashboard	Nothing. No external account.

Add it

Open Components and click Helpdesk under Post Processing.
Connect End to it so the transcript goes into the ticket.
Add a Structured Output node after End that extracts the caller’s email, and connect it to the Helpdesk node. That links HubSpot tickets to the right contact and records the requester on internal tickets.

End ─────────────────────────────▶ Helpdesk
End ──▶ Structured Output (email) ──▶

Setting	What to enter
Where to file tickets	HubSpot Tickets or This dashboard. Default HubSpot Tickets.
Subject	The ticket title. Default “Voice call follow-up”.
Priority	Low, Medium or High. Default Medium.
Email Field	The Structured Output field or input variable that holds the requester’s email. Default email.
HubSpot Pipeline ID (More settings)	Only for HubSpot. Default 0.
HubSpot Pipeline Stage ID (More settings)	Only for HubSpot. Default 1.

No HubSpot token: the step is skipped. The call is unaffected.
No email found: a HubSpot ticket is still created, just not linked to a contact. An internal ticket has no requester.
Contact lookup fails: the ticket is created unlinked rather than lost.