Short answer: You can speech to text in ElevenLabs by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ElevenLabs Speech to Text 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 |
|---|---|---|---|
Audio File URL file_url | string | Required | Audio File URL (required) |
Model model_id | options | Optional | Model. Options: Scribe v1 |
Language Code language_code | string | Optional | en (auto-detect if blank) |
Speaker Diarization diarize | options | Optional | Speaker Diarization. Options: No, Yes |
Timestamp Granularity timestamps_granularity | options | Optional | Timestamp Granularity. Options: None, Word, Character |
{"file_url": "e.g. https://example.com/path","model_id": "{{trigger.model_id}}","language_code": "en (auto-detect if blank)","diarize": "{{trigger.diarize}}","timestamps_granularity": "{{trigger.timestamps_granularity}}"}
{"text": "Hello world","words": [{"end": 0.4,"text": "Hello","type": "word","start": 0}],"language_code": "en","language_probability": 0.99}
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.