Short answer: Drop the "Play.ht → Play.ht Text to Speech" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
Triggered by anything in the catalog. Free tier available. No credit card.