PActionPlay.htUpdated September 2026
How do I generate speech with Play.ht?
Short answer: You can play.ht text to speech in Play.ht by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Play.ht Play.ht Text to Speech action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
Text text | string | Required | Text (required) |
Voice voice | string | Required | Voice s3 URI or voice id |
Engine voice_engine | options | Optional | Engine. Options: Play 3.0 Mini, PlayHT 2.0 |
Format output_format | options | Optional | Format. Options: MP3, WAV, OGG |
Speed speed | string | Optional | Speed |
Sample request
{"text": "{{trigger.text}}","voice": "{{trigger.voice}}","voice_engine": "{{trigger.voice_engine}}","output_format": "{{trigger.output_format}}","speed": "{{trigger.speed}}"}
Returns
{"audio": "<binary>"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Play.ht Text to Speech.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Play.ht Text to Speech.
What does the Play.ht Text to Speech action do in Play.ht?
Generates audio from text with chosen voice. Affordable TTS for voice-agent and narration workflows. Competitive alternative to ElevenLabs at SMB pricing.
What inputs does Play.ht Text to Speech require?
Required: Text, Voice. 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 run history shows the failed step with its input and the error message Play.ht returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Play.ht Text to Speech support batch operations?
Run Play.ht Text to Speech inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Play.ht's rate limits.
More actions