FlowiseAI/Flowise

[FEATURE] Add support for Azure Speech-To-Text custom endpoint

Open

#3,767 opened on Dec 26, 2024

View on GitHub
 (4 comments) (0 reactions) (0 assignees)TypeScript (24,335 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (52,823 stars)
PR merge metrics
 (Avg merge 8d 6h) (15 merged PRs in 30d)

Description

Describe the feature you'd like Currently is possible to enable the Azure STT standard endpoint. Supporting a custom endpoint will enable the usage of Azure STT tailored for specific languages (dialects, engineering, healthcare, etc)

Additional context Calling the custom endpoint require this code var config = SpeechSDK.SpeechConfig.fromSubscription("YourSubscriptionKey", "YourServiceRegion"); config.endpointId = "YourEndpointId"; var reco = new SpeechSDK.SpeechRecognizer(config);

Where YourSubscriptionKey and YourServiceRegion parameters are already available in Flowise configuration, what is missing is the YourEndpointId

Contributor guide

Research direction
Find the existing Azure STT configuration in Flowise, locate where subscription key and region are used, and add a new config field for endpointId. Update the relevant components to pass endpointId to the SpeechSDK.SpeechConfig.fromSubscription call.
Tech stack
typescriptnodejs
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitTypeScriptAzure Speech SDK
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65