Get Voice: ElevenLabs action

Inputs

The fields this action accepts.

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	Voice ID. Example: 21m00Tcm4TlvDq8ikWAM

Sample request

{
  "voice_id": "e.g. 21m00Tcm4TlvDq8ikWAM"
}

Returns

{
  "name": "Rachel",
  "labels": {
    "age": "young",
    "accent": "American",
    "gender": "female"
  },
  "category": "premade",
  "voice_id": "21m00Tcm4TlvDq8ikWAM"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Voice.

What does the Get Voice action do in ElevenLabs?

Returns a voice's metadata — name, gender, age, accent, description. Useful for "show me the voice configuration before generating" workflows.

What inputs does Get Voice require?

Required: Voice ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if ElevenLabs returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Voice support batch operations?

Yes. Run Get Voice inside a Loop node to process arrays. Tiny Command handles ElevenLabs's rate limits automatically so you don't have to throttle manually.

More actions