Short answer: You can cartesia sonic tts in Cartesia by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Cartesia Cartesia Sonic TTS action to a workflow, map its 4 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 transcript | string | Required | Text (required) |
Voice ID voice_id | string | Required | Voice ID (required) |
Model model_id | options | Optional | Model. Options: Sonic 2, Sonic |
Language language | string | Optional | Language |
{"transcript": "{{trigger.transcript}}","voice_id": "{{trigger.voice_id}}","model_id": "{{trigger.model_id}}","language": "{{trigger.language}}"}
"<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.