Resources · n8n integration

Botnoi Voice n8n integrationAutomate Botnoi Voice with n8n.

The Botnoi Voice n8n integration turns a text field into an audio file without leaving the workflow. The node carries one resource and a single operation, Generate voice, and has no trigger of its own. One action, so the setup stays short, and the audio never needs a manual export step.

Community node This node is not shipped with n8n: it is a community package (n8n-nodes-botnoi-voice) you install from Settings › Community nodes on a self-hosted instance. npm

Try the Botnoi Voice integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Botnoi Voice n8n integration actually give you?

Botnoi Voice is a text to speech service. Inside n8n, the node exposes it as one action: text goes in, audio comes back. The workflow decides what happens next, an email attachment, a file in storage, a message in a channel.

Because the call happens in the same execution as the data that produced the text, the audio never needs a manual export step.

First scenario, a spoken daily digest. A Schedule Trigger reads yesterday's rows from Google Sheets, one sentence per row is assembled and passed as an expression, and voice.generate returns an MP3 that lands in a Slack channel before the morning stand up.

Second scenario, a spoken reply to an inbound message. A Gmail message starts the run, the part worth reading out loud is kept, and the node renders it with a V2 speaker so the recipient gets a short audio file instead of another wall of text.

Third scenario, one announcement in several markets. The same source string goes through the node more than once with a different Language value each time, Thai, then Spanish, then English, which produces one audio file per market from a single piece of copy.

The node does speech generation and stops there. Anything else the Botnoi Voice API exposes has to go through the HTTP Request node, which calls any endpoint of that API and reuses the same credential through predefined authentication. That split keeps the dedicated node short to configure and leaves everything else to a generic call.

Two limits are worth knowing before building. The package is a community node, so it installs on a self-hosted instance, while n8n Cloud only accepts verified community nodes. And there is no Botnoi Voice trigger, meaning every workflow starts somewhere else: a Schedule Trigger on a fixed interval, an n8n Webhook (a URL a third party service calls) or the trigger of another tool. If the platform choice is still open, the n8n review works through it in detail.

Connect

How do you connect Botnoi Voice to n8n?

  1. 01

    Install the community package

    The node is not bundled with n8n. On a self-hosted instance, open Settings, then Community nodes, and install the npm package n8n-nodes-botnoi-voice (version 2.0.7). Once the install finishes, Botnoi Voice shows up in the node panel like any other node. On n8n Cloud the same step only works for verified community nodes.

  2. 02

    Create the credential once

    Open the Credentials menu in n8n and create the Botnoi Voice credential there. A credential is stored at instance level, so it gets created once and reused across every workflow that talks to the service. No copy and paste of keys from one node to the next, and no secret sitting inside a workflow export.

  3. 03

    Pick the credential in the node

    Drop the Botnoi Voice node onto the canvas and choose the credential in its dropdown list, which already shows what the instance holds. Then set the operation to Generate voice, fill Text, and run the node once on a short sentence. A successful run returns the audio and confirms the install and the credential in one go.

Actions

What the Botnoi Voice node can do

The Botnoi Voice node exposes 1 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGenerate
Voice✓

Voice

1 operation
01

Generate voice

voice.generate

What you see in n8n

Notes & use cases

Sends text to the Botnoi Voice API and returns the generated speech in the chosen format, ready for whatever node comes next.

Key parameters

  • Text: required, the text to convert to speech, most often {{ $json.text }} when it comes from an earlier node. Left empty, it stops the execution.
  • Speaker Version then Speaker (V1) or Speaker (V2): choose the voice catalog, then the voice inside it.
  • Language: the language of the input text, Thai, Japanese, Spanish, French and English among others.
  • Media Type: MP3 or WAV output. Volume and Speed adjust the reading.
Use cases
reading a support answer out loud, or rendering a WAV file for a phone system.
Need help

Need help automating Botnoi Voice with n8n?

A person reads every message.

FAQ

Botnoi Voice and n8n, common questions

01Is the Botnoi Voice n8n integration free?
On the n8n side, yes. n8n costs nothing extra for this node, and the node itself is a community package, the npm package n8n-nodes-botnoi-voice in version 2.0.7. It is not bundled with n8n: you install it from Settings, then Community nodes, on a self-hosted instance. n8n Cloud only accepts verified community nodes, so the hosting choice decides whether the install is possible at all. What the Botnoi Voice service charges for speech generation is a separate matter and is not covered here. Self-hosting n8n with Docker or npm and using n8n Cloud produce the same workflow, the difference is where it runs.
02What credentials do you need for Botnoi Voice in n8n?
One Botnoi Voice credential, created from the Credentials menu in n8n. The node has no authentication selector of its own: it simply offers the credentials stored on the instance in a dropdown list. A credential is written once and reused by every workflow, so a second or third Botnoi Voice node needs no extra setup. Keep the install order in mind: the community package has to be present before the node, and therefore its credential type, shows up in the interface. The exact field labels of that credential are not documented in the source used for this page, so check them in n8n when you create it.
03What are the limits of the Botnoi Voice node in n8n?
The node exposes one resource and one operation, Generate voice. That covers speech generation and nothing else, so any other endpoint of the Botnoi Voice API is out of reach from this node. The answer there is the HTTP Request node, which calls any endpoint of the API and reuses the same credential through predefined authentication. Two more points: the node is at version 1 and comes from a community package rather than from n8n, which means updates follow the package, not the n8n release cycle. And with no trigger available, the node can only ever sit in the middle of a workflow, never at its start.
04Can a workflow react in real time without a Botnoi Voice trigger?
Yes, as long as something else starts it. Botnoi Voice has no trigger node in n8n, so the workflow begins with another starting point and the generation happens downstream. Three options cover most cases. A Schedule Trigger runs the workflow on a fixed interval, which fits digests and batches. An n8n Webhook gives you a URL that a third party service calls when an event happens, which is the closest thing to instant reaction. Or the trigger of another tool already in the workflow starts the run, a new row, a new message, a new ticket. The Botnoi Voice node then receives the text through an expression.
05n8n or Make for Botnoi Voice?
It depends on three criteria, and neither platform is a bad answer. Hosting comes first: n8n can be self-hosted with Docker or npm, or used on n8n Cloud, while Make is a hosted platform with no self-hosting option. Data control follows from that, since a self-hosted instance keeps the audio and the source text on your own infrastructure. The cost model differs too, Make being billed per operation. One detail matters here specifically: Botnoi Voice reaches n8n through a community package, so the self-hosted route is the one that makes the node available at all.
Same platform

Other docs you might need on this stack.

Browse all integrations