- Google Cloud Text-to-Speech
- Connect Google Cloud Text-to-Speech to Boost.space Integrator
- Create and configure a Google Cloud Console project for Google Cloud Text-to-Speech.
- Create a Google Cloud Console project for Google Cloud Text-to-Speech
- Enable APIs for Google Cloud Text-to-Speech
- Configure your OAuth consent screen for Google Cloud Text-to-Speech
- Create your Google Cloud Text-to-Speech client credentials
- Establish the connection with Google Cloud Text-to-Speech in Boost.space Integrator
- Build Google Cloud Text-to-Speech Scenarios
- Connect Google Cloud Text-to-Speech to Boost.space Integrator
Active |
---|
This application does not need additional settings. So you can make connection only by using your login credentials or by following the instructions below . |
With Google Cloud Text-to-Speech modules in Boost.space Integrator, you can convert text or Speech Synthesis Markup Language (SSML) input into audio data of natural human speech in your Google Cloud Text-to-Speech account.
To use the Google Cloud Text-to-Speech module, you must have a Google account, a project created in the Google Cloud Console, and billing enabled for the Google project. You can create an account at accounts.google.com.
Refer to the Google Cloud Text-to-Speech API documentation for a list of available endpoints.
Note | |
---|---|
Boost.space Integrator‘s use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy. |
To establish the connection, you must:
Before you establish the connection in Boost.space Integrator, you must create and configure a project in the Google Cloud Console to obtain your client credentials.
To create a Google Cloud Console project:
-
Log in to the Google Cloud Console using your Google credentials.
-
In the top menu, click Select a project > New project.
-
Enter a Project name and select the Location for your project.
-
Click Create.
-
In the top menu, check if your new project is selected in the Select a project dropdown. If not, select the project you just created.
To enable to required API:
To configure your OAuth consent screen:
-
In the left sidebar, click OAuth consent screen.
-
Under User Type, select External.
For more information regarding user types, refer to Google’s Exceptions to verification requirements documentation.
-
Click Create.
-
Fill in the required fields with your information.
-
In the Authorized domains section, add
make.com
andboost.space
. -
Click Save and continue.
-
In the Scopes page, click Add or remove scopes, add the following scope, and click Update:
https://www.googleapis.com/auth/cloud-platform
-
Click Save and continue.
-
Optional: If your project will remain in the Testing publishing status, add test user emails on the Test users page, then click Save and continue.
To create your client credentials:
-
In the left sidebar, click Credentials.
-
Click + Create Credentials > OAuth client ID.
-
In the Application type dropdown, select Web application.
-
Update the Name of your OAuth client. This will help you identify it in the console.
-
In the Authorized redirect URIs section, click + Add URI and enter the following redirect URI:
https://integrator.boost.space/oauth/cb/google-custom
. -
Copy your Client ID and Client secret values and store them in a safe place.
You will use these values in the Client ID and Client Secret fields in Boost.space Integrator.
To establish the connection in Boost.space Integrator:
-
Log in to your Boost.space Integrator account, add a Google Cloud Text-to-Speech module to your scenario, and click Create a connection.
-
Optional: In the Connection name field, enter a name for the connection.
-
In the Client ID and Client Secret fields, enter the values you copied in the Create your Google Cloud Text-to-Speech client credentials section above.
-
Click Sign in with Google.
-
If prompted, authenticate your account and confirm access.
You have successfully established the connection. You can now edit your scenario and add more Google Cloud Text-to-Speech modules. If your connection requires reauthorization at any point, follow the connection renewal steps here.