> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/workflow-builder/outputs/audio-node.md).

# Audio Node

### What is an Audio Node?

The Audio node lets you generate audio from text using high-quality voice synthesis models. It's ideal for turning responses from LLMs or static text into spoken audio.

This node is commonly used in voice interfaces, accessibility workflows, or any experience where you want to deliver output via sound.

It supports popular text-to-speech engines and customizable voices to match your tone and use case.

Key capabilities include:

* Supports multilingual audio synthesis.
* Choose from multiple voice models and accents.
* Play back audio directly in the interface with **Test Output**.
* Optionally use your own API key to connect with external TTS providers.

### How to use it?

To use the Audio node:

* **Input:** Accepts a text string (e.g., from an LLM or Input node).
* **Output:** Returns a playable audio file that can be previewed that can be previewed.

After receiving text input, the Audio node displays a **Test Output** section with a play button, allowing you to listen to the generated audio.

### Settings

#### Configuration Options

* **Model:** Choose the TTS engine, such as `eleven_multilingual_v2`.
* **Voice:** Select from available voice profiles (e.g., Sarah, Chris).
* **API Key:** Optional field for providing your own TTS provider credentials.

### How to expose Audio externally?

To make audio results available in your external interface:

1. Go to the **Export** tab.
2. Enable the Audio node in the **Outputs** section under **Fields**.
3. Click **Save Interface**.
4. When triggered, users will be able to hear the generated audio directly in the interface.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stackai.com/workflow-builder/outputs/audio-node.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.