PActionPlay.htUpdated May 2026

How do I clone a voice with Play.ht?

Short answer: Drop the "Play.ht → Play.ht Clone Voice" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Play.ht 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
Audio Sample URL sample_file_url	string	Required	Single sample, 10s+ recommended
Voice Name voice_name	string	Required	Voice Name (required)

Sample request

{
  "sample_file_url": "e.g. https://example.com/path",
  "voice_name": "{{trigger.voice_name}}"
}

Returns

{
  "id": "clone_abc",
  "name": "My Voice",
  "type": "instant"
}

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

Triggered by

Apps that pair well as the trigger for Play.ht Clone Voice.

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

Google Sheets → Play.ht

2 Google Sheets triggers

HubSpot → Play.ht

18 HubSpot triggers

FAQ

Questions about Play.ht Clone Voice.

What does the Play.ht Clone Voice action do in Play.ht?

Instant voice clone from 30-60 seconds of sample audio. Returns a custom voice ID usable in subsequent TTS calls. For brand-consistent narration at scale.

What inputs does Play.ht Clone Voice require?

Required: Audio Sample URL, Voice Name. 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 Play.ht 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 Play.ht Clone Voice support batch operations?

Yes. Run Play.ht Clone Voice inside a Loop node to process arrays. Tiny Command handles Play.ht's rate limits automatically so you don't have to throttle manually.

More actions