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.
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 |
{"text": "{{trigger.text}}","voice": "{{trigger.voice}}","voice_engine": "{{trigger.voice_engine}}","output_format": "{{trigger.output_format}}","speed": "{{trigger.speed}}"}
{"audio": "<binary>"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.