Genesys Cloud - Developer Community!

 View Only

Sign Up

  • 1.  Architect Dependency Search for voices

    Posted 14 hours ago

    I am looking to filter the selection down to just the voices that are already being used in the different Architect Flows.

    Can you please help me in getting that?

    In Dependency Search we can use filter for Text to Speech Engine => Genesys Enhanced TTS => Select a voice 

    Need the list of voices used in the org (Full list not required) 


    #Architect

    ------------------------------
    AJAY KUMAR
    ------------------------------


  • 2.  RE: Architect Dependency Search for voices

    Posted 13 hours ago

    Hi Ajay,

    From my understanding, I don't believe there's currently a built-in way to generate a consolidated list of only the TTS voices referenced across all Architect flows. The Dependency Search feature allows you to search by TTS engine and voice to identify which flows use that combination, but I haven't found a report or API that returns the unique set of voices currently in use across an organisation. If anyone has found a different approach, I'd be interested as well. Following this post.

    Resources:



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 3.  RE: Architect Dependency Search for voices

    Posted 4 hours ago

    Is it possible via Archy or with the help of API's?



    ------------------------------
    AJAY KUMAR
    ------------------------------



  • 4.  RE: Architect Dependency Search for voices

    Posted 4 hours ago
    Based on the current documentation, there isn't a native way to retrieve a consolidated list of all TTS voices currently in use across an organization.
     
    The supported method is Dependency Search, which lets you search by TTS Engine and Voice, but only one voice at a time.
     
    If you need to automate this, you could export the flow definitions with Archy or retrieve them through the Architect APIs and parse the exported YAML/JSON to extract the configured TTS voices. This isn't a built-in capability, but it can be achieved with a custom solution.
     
    Since this seems like a common administrative need, it might also be worth submitting an enhancement request through the Genesys Cloud Ideas Portal. A native report or API endpoint that returns the distinct TTS voices referenced across all Architect flows would simplify audits, voice migrations, and ongoing TTS administration.


    ------------------------------
    Raphael Poliesi
    ------------------------------