Generate Sound Effect: 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
Prompt text	string	Required	Cinematic thunder rumble, 5 seconds
Duration (seconds) duration_seconds	string	Optional	0.5 to 22, blank = auto
Prompt Influence prompt_influence	string	Optional	0-1

Sample request

{
  "text": "Cinematic thunder rumble, 5 seconds",
  "duration_seconds": "0.5 to 22, blank = auto",
  "prompt_influence": "0-1"
}

Returns

{
  "audio": "<binary>"
}

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

FAQ

Questions about Generate Sound Effect.

What does the Generate Sound Effect action do in ElevenLabs?

Generates short audio effects from a text prompt ("door creak", "thunder", "applause"). Useful for video production workflows that need sound effects alongside generated narration.

What inputs does Generate Sound Effect require?

Required: Prompt. 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 Generate Sound Effect support batch operations?

Yes. Run Generate Sound Effect 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