Build with

Create one follow-up ticket for a confirmed customer request and verify that it reaches the intended owner. This walkthrough uses a HubSpot ticket with explicit pipeline, stage and owner IDs. A saved record does not prove that an email was sent or a representative accepted the request.

Before you begin

  • A test project with HubSpot CRM action OAuth.
  • A HubSpot administrator supplies an allowed pipeline ID, a stage ID belonging to that pipeline, and an active permitted owner ID. Confirm the owner can see and act on tickets there. Labels and email addresses are not substitutes for those IDs.
  • A customer-confirmed request, its contact preference and a backend place to retain the customer/request/ticket mapping. Reuse an existing request ID for later updates.

Studio

Open your test project in Agent studio and prepare the follow-up Playbook or Workflow.

Code

Use a Voiceflow bearer credential with access to this project and test Environment; keep it on your backend. Set VF_TOKEN, PROJECT_ID and ENVIRONMENT before using the commands. Standalone execution uses the Environment’s Draft. For native CRM actions, complete the browser OAuth in the prerequisite manual even when working through Code.

Record and route the request

1

Confirm the request and destination

Summarize the request, the information the team will receive and the contact expectation your team has approved. The example records a 25-seat demo enquiry. Ask for confirmation before creating the ticket. Use the administrator-approved destination rather than allowing the model to invent an owner ID.

2

Create the ticket with explicit routing

Studio

Add HubSpot → Create ticket. Supply subject, content, hs_ticket_priority, hs_pipeline, hs_pipeline_stage and hubspot_owner_id using the approved IDs. Run after confirmation and inspect the actual ticket ID in Capture response.

Code

Set PIPELINE_ID, STAGE_ID and OWNER_ID to the administrator-provided values before this call:

Require success: true, error: null and truncated: false; keep output.data.ticket.id. These are project Draft-connection writes to a real provider account when you execute them.

Pass the explicit stage: omission defaults to 1, which may not belong to your pipeline. The action sets source_type: FORM and does not associate the ticket to a Contact automatically. Retain that customer mapping in your backend rather than assuming text in the ticket creates the relationship.

3

Verify the work item and tell the customer

Open the returned ticket in HubSpot. Check pipeline, stage, owner, priority and exact confirmed request content. Have the intended team confirm visibility. Record the ticket ID against the request, then give the customer the approved acknowledgement. If routing is wrong, reconcile and repair this existing ticket through your administrator’s approved process; creating another ticket does not repair the first one.

Verify routing and failure handling

Test one normal request, declined confirmation, an invalid owner/stage and an ambiguous timeout. Confirm one ticket reaches the approved owner; failed/cancelled paths do not falsely report success. Reconcile the CRM before retrying an uncertain create.

For Salesforce, Case actions create and update Cases and comments. Their schemas do not expose OwnerId or Status updates. Use a tested org routing process or the manual’s separately authorized ownership request when explicit assignment is required. Use Human agent hand-off for an immediate two-way conversation rather than treating ticket creation as a live transfer.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.