Short answer: You can text to speech in ElevenLabs by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ElevenLabs Text to Speech action to a workflow, map its 6 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 |
|---|---|---|---|
Voice ID voice_id | string | Required | The voice to use. Find voice IDs via the List Voices operation or your ElevenLabs dashboard. |
Text text | string | Required | The text to convert to speech (max 5000 chars for standard plan) |
Model model_id | options | Optional | Model. Options: Multilingual v2 (highest quality), Turbo v2.5 (low latency), Monolingual v1 (English only) |
Stability stability | string | Optional | Voice stability (0.0 to 1.0). Lower = more expressive, higher = more consistent. |
Similarity Boost similarity_boost | string | Optional | Voice clarity and similarity (0.0 to 1.0). Higher = closer to original voice. |
Output Format output_format | options | Optional | Output Format. Options: MP3 (44.1kHz, 128kbps), MP3 (44.1kHz, 192kbps), PCM (16kHz), PCM (44.1kHz) |
{"voice_id": "e.g. 21m00Tcm4TlvDq8ikWAM","text": "e.g. Hello, welcome to our platform. We're glad to have you here.","model_id": "{{trigger.model_id}}","stability": "e.g. 0.5","similarity_boost": "e.g. 0.75"}
{"note": "Binary audio data — pipe to a file or downstream service","content_type": "audio/mpeg"}
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.