Google Developer

1. Overview

The Google Developer tool integrates with the Google Play Developer API, allowing you to programmatically manage your application's presence on the Google Play Store. Its primary function is to interact with user feedback and application data.

With the GoInsight Google Developer node, you can automate the entire lifecycle of managing user reviews for your Android applications. This enables you to build workflows that monitor feedback, respond to users, and analyze sentiment directly within your automated processes. Key capabilities include:

• Fetching reviews individually by their unique ID.
• Listing all reviews for an application, with support for pagination.
• Replying directly to user reviews to engage with your community.

2. Prerequisites

Before using this node, you need to have the following:

• A valid Google Developer account with an application published on the Google Play Store.
• Appropriate permissions within your Google Cloud project and Google Play Console to create and manage API credentials (OAuth 2.0 client IDs) that have access to the Google Play Developer API.

3. Credentials

For a detailed guide on how to obtain and configure your credentials, please refer to our official documentation: Credentials Configuration Guide.

4. Supported Operations

Summary

This node primarily operates on the Review resource.

Operation Details

Get a Review

Retrieves a specific review from the Google Play Developer API for the specified application.

Input Parameters:

• PackageName: Android application package name in reverse domain format (e.g., 'com.example.myapp'). How to find: 1) In Google Play Console, go to your app's dashboard - the package name is shown in the URL and app details. 2) On Google Play Store, the package name is in the URL: play.google.com/store/apps/details?id=.
• ReviewId: The unique identifier of the review to retrieve. Format: string starting with 'gp:' prefix (e.g., 'gp:AOqpTOHxABCDEFGH1234567890'). How to find: Call the List Review action to get all review IDs for your app, or find them in Google Play Console under Reviews section.

Options:

• TranslationLanguage: ISO 639-1 language code to translate the review content (optional, empty for no translation). Common codes: en (English), zh (Chinese), ja (Japanese), ko (Korean), es (Spanish), fr (French), de (German).

Output:

• ReviewId (string): The unique identifier of the review (e.g., 'gp:AOqpTOHxABCDEFGH1234567890').
• AuthorName (string): The display name of the review author as shown on Google Play.
• Text (string): The text content of the review. If TranslationLanguage was specified, this contains the translated text.
• LastModified (string): Timestamp when the review was last modified, in 'seconds.nanos' format (e.g., '1706284800.000000000'). Convert seconds part to datetime for human-readable format.
• StarRating (number): The star rating of the review, integer from 1 (worst) to 5 (best).
• ReviewerLanguage (string): The language code of the review content (ISO 639-1, e.g., 'en', 'zh', 'ja').
• Device (string): The device name of the reviewer (e.g., 'Samsung Galaxy S21', 'Google Pixel 7').
• AndroidOsVersion (number): Android API level of the reviewer's device (e.g., 30 = Android 11, 33 = Android 13).
• AppVersionCode (number): The integer version code of the app when the review was submitted (e.g., 123).
• AppVersionName (string): The version name string of the app when the review was submitted (e.g., '1.2.3').
• ThumbsUpCount (number): The number of users who found this review helpful (thumbs up).
• ThumbsDownCount (number): The number of users who found this review unhelpful (thumbs down).
• DevCommentText (string): The developer's reply text to this review. Empty string if no reply has been posted.
• DevCommentLastModified (string): Timestamp when the developer's reply was last modified, in 'seconds.nanos' format. Empty string if no reply.
• DeviceMetadata (object): Device metadata object containing hardware details. Common fields: manufacturer (string, e.g., 'Samsung'), model (string, e.g., 'Galaxy S21'), screenDensity (number, DPI), screenWidth (number, pixels), screenHeight (number, pixels). Empty object {} if not available.
• OriginalStatusCode (number): The original HTTP status code returned by the Google Play API. Default 0 means the request did not reach upstream (e.g., timeout or exception). Use for debugging.
• StatusCode (number): Operation status code: 200=Success (check ErrorMessage for business errors), -1=Parameter validation error, 500=System error (network timeout/connection failure).
• ErrorMessage (string): Detailed error message if any error occurred. Empty string if the operation succeeded.

List Review

Retrieves a list of reviews for the specified Android application via Google Developer API.

Input Parameters:

• PackageName: Android application package name in reverse domain format (e.g., 'com.example.myapp'). Prerequisites: You must have a published app in Google Play Console. How to find: 1) In Google Play Console, go to All apps, the package name is shown under each app title. 2) On Google Play Store URL: play.google.com/store/apps/details?id=.

Options:

• Token: Pagination token for fetching the next page of reviews. Leave empty for the first request (as shown in RequestExample). Use the NextPageToken value from a previous response to get the next page. Example of a token: 'CgkKBwoFZW4tVVM'. This is the recommended way to paginate through reviews.
• MaxResult: Maximum number of reviews to return per request (positive integer). Google Play API typically returns up to 100 reviews per page. Example: 50.
• TranslationLanguage: ISO 639-1 language code to translate review text (optional, empty for original language). Common codes: en (English), zh (Chinese), ja (Japanese), ko (Korean), es (Spanish), fr (French), de (German). For a complete list of supported language codes, see: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes

Output:

• Reviews (object-array): Array of review objects as returned by Google Play API. Each review object contains: reviewId (string, unique review ID starting with 'gp:'), authorName (string, reviewer's display name), comments (array of comment objects). Each comment contains either userComment or developerComment. userComment fields: text (string), starRating (number, 1-5), reviewerLanguage (string), device (string), androidOsVersion (number), appVersionCode (number), lastModified (object with seconds/nanos).
• NextPageToken (string): Pagination token for retrieving the next page of reviews. Empty string if no more pages. Pass this value as the Token input parameter to fetch the next page.
• OriginalStatusCode (number): The original HTTP status code returned by the Google Play API. Default 0 means the request did not reach upstream (e.g., timeout or exception). Use for debugging.
• StatusCode (number): Operation status code: 200=Success (check ErrorMessage for business errors), -1=Parameter validation error, 500=System error (network timeout/connection failure).
• ErrorMessage (string): Detailed error message if any error occurred. Empty string if the operation succeeded.

Reply a Review

Replies to a specific Google Play Store in-app review. This is a write action: the reviewer will receive a push notification from Google Play after you reply. Always verify the target review and set Confirm=true only when you really want to post the reply.

Input Parameters:

• PackageName: Android application package name in reverse domain format (e.g., 'com.example.myapp'). How to find: 1) In Google Play Console, go to All apps, the package name is shown under each app title. 2) On Google Play Store URL: play.google.com/store/apps/details?id=.
• ReviewId: The unique identifier of the review to reply to. Format: string starting with 'gp:' prefix (e.g., 'gp:AOqpTOHxABCDEFGH1234567890'). How to find: Call the List Review or Get a Review action to get review IDs for your app.
• Confirm: Safety gate for this write action. Must be true to send a real developer reply to Google Play. Use false to block accidental writes in automation or testing.
• ReplyText: The text content of the reply to post. Character limit: up to 350 characters. Supports emoji and line breaks. Example: 'Thank you for your feedback! We have fixed the issue in version 2.1.'

Output:

• Result (object): Structured reply result object. Contains: ReplyText (string, the reply content you posted) and LastEdited (number, Unix timestamp in seconds UTC when the reply was last edited). Empty object {} if the operation failed.
• OriginalStatusCode (number): The original HTTP status code returned by the Google Play API. Default 0 means the request did not reach upstream (e.g., timeout or exception). Use for debugging.
• StatusCode (number): Operation status code: 200=Success (check ErrorMessage for business errors), -1=Parameter validation error, 500=System error (network timeout/connection failure).
• ErrorMessage (string): Detailed error message if any error occurred. Empty string if the operation succeeded.

5. Example Usage

This section will guide you through creating a simple workflow to fetch the latest reviews for your Android application.

The workflow will consist of three nodes: Start -> Google Developer: List Review -> Answer.

1. Add the Tool Node

• In the workflow canvas, click the + button to add a new node.
• Select the "Tool" tab in the pop-up panel.
• Find and select "Google Developer" from the list of tools.
• From the list of supported operations for Google Developer, click on "List Review" to add the node to your canvas.

2. Configure the Node

• Click on the newly added "List Review" node to open its configuration panel on the right.
• Credentials Configuration: At the top of the panel, find the credentials field. Click the dropdown menu and select your pre-configured Google Developer credentials.
• Parameter Configuration: Fill in the required parameters to specify which reviews to fetch.
  • PackageName: Enter the unique package name of your application, for example, com.yourcompany.yourapp.
  • MaxResult (Optional): To limit the number of reviews returned, you can enter a number here, such as 10. If left blank, the API's default limit will be used.

3. Run and Validate

• Once all required parameters are correctly filled, any error indicators on the workflow canvas should disappear.
• Click the "Test Run" button in the top-right corner of the canvas to execute the workflow.
• After a successful execution, you can click the logs icon in the top-right corner to view the detailed inputs and outputs of the node, verifying that the reviews were fetched correctly.

After completing these steps, your workflow is fully configured. When you run it, it will connect to the Google Play Developer API and retrieve a list of the most recent reviews for your specified application.

6. FAQs

Q: I'm receiving a 401 Unauthorized or 403 Forbidden error. What could be the cause?

A: These errors typically indicate an issue with your credentials or permissions. Please check the following:

• Correct Credentials: Ensure you have selected the correct Google Developer credentials in the node configuration.
• API Enabled: Verify that the "Google Play Android Developer API" is enabled in your Google Cloud project.
• OAuth Consent Screen: Make sure your OAuth consent screen is properly configured and that your application is not in "testing" mode if you are using production credentials.
• Permissions: The user account used to generate the credentials must have sufficient permissions in the Google Play Console to access reviews.

Q: How do I process the Reviews output from the "List Review" action?

A: The Reviews output is an array of objects returned directly by the Google Play API. Each object already contains fields such as reviewId, authorName, and comments, so you can access them directly in downstream nodes without JSON.parse().

Q: How do I handle pagination to get all reviews?

A: The "List Review" operation supports pagination. If there are more reviews to fetch, the NextPageToken output field will contain a value. To get the next page, add another "List Review" node (or create a loop) and pass the NextPageToken from the first node's output into the Token input parameter of the second node. Repeat this process until the NextPageToken output is empty.

7. Official Documentation

For more in-depth information about the API's capabilities and parameters, please refer to the official documentation:

Google Play Developer API Documentation