Generate Brazilian Portuguese WAV with Brainiall TTS

This manual Node-RED flow turns one explicitly supplied text into a WAV file with Brainiall's hosted Brazilian Portuguese voice pf_dora. It uses only Node-RED core nodes: Inject, Function, HTTP Request, and Debug.

Who it is for

Automation builders who need Brazilian Portuguese narration, accessibility audio, spoken alerts, or a reproducible TTS step without operating a speech model or GPU.

Setup

1. Create a Brainiall API key at https://app.brainiall.com?utm_source=node_red&utm_medium=flow_library&utm_campaign=c19_tts_wav.
2. Set that key as the BRAINIALL_API_KEY environment variable in the Node-RED runtime. Do not paste it into a node or the exported flow.
3. Import flow.json, deploy it, edit the manual Inject text if needed, and click Inject.
4. Inspect the Debug result. Success contains only status, byte count, character count, and voice ID. The WAV remains in msg.payload so you can connect a File, cloud-storage, or playback node. The flow deliberately does not log the submitted text, API key, or returned audio.

Run npm test before importing a modified copy. The dependency-free validator checks the flow graph, the manual-only trigger, endpoint and voice allow-list, credential hygiene, fail-closed WAV validation, and metadata-only Debug node.

Boundaries and cost

• The flow does not run automatically.
• It accepts 1 to 5,000 characters per invocation.
• Text is uploaded to https://api.brainiall.com/v1/tts/synthesize only after the user clicks Inject.
• Synthesis is metered at USD 0.008 per 1,000 characters against the caller's Brainiall balance.
• The response must be HTTP 200, at least 44 bytes, and contain both RIFF and WAVE markers. Otherwise the flow fails closed.
• This is an API client, not an offline TTS engine. Review Brainiall's current service and privacy terms before sending sensitive text.

Attribution and revenue proof

The signup URL carries utm_source=node_red, utm_medium=flow_library, and utm_campaign=c19_tts_wav. A Flow Library view, import, owner QA, successful request, trial, or signup is not revenue. Revenue requires a buyer-linked payment that is received, settled, and reconciled.

License

MIT. See LICENSE.