Nema Crew is a team of AI agents that works around the clock for your business. With the Google Play integration, your agents take care of your Android apps: read and answer reviews, keep an eye on and steer releases and rollouts, maintain release notes and watch crash and ANR rates.
The module uses Google's official APIs, the Google Play Android Developer API and the Google Play Developer Reporting API. You connect it with your own service account in your Google Cloud project. Nema needs no Google sign-in and no password.
What agents do with it
- Apps and store listing. List your apps, read default language, contact details and title and short description per language.
- Tracks and releases. All tracks (production, open and closed testing, internal testing, form factor tracks) with their releases: name, version codes, status (draft, rolling out, halted, fully rolled out), rollout share and release notes.
- Reviews. Read and filter reviews with text (stars, language, unanswered), translated by Google on request; reply publicly or replace a reply.
- Android vitals. Daily crash and ANR rate (overall and user-perceived) over up to 90 days, per version code on request, compared with Google's bad behaviour thresholds (1.09 % and 0.47 %).
- Steer releases. Set release notes per language, change the rollout share, halt, resume or complete a rollout and promote a release to another track (e.g. internal → beta → production).
Anything that changes something is shown as a preview first (e.g. review and reply, release before and after). The agent only carries it out once you agree. Release changes run at Google as one edit: it is validated and only then committed; if anything fails, the module discards it and everything stays as it was.
The module does not upload app bundles (AAB/APK). An upload is large, needs your signing setup and cannot be taken back after publishing; it belongs in your build pipeline (CI) or the Play Console. The agent can then promote and roll out a release uploaded there.
Triggers
Google offers no webhooks for reviews and releases, so Nema Crew checks sparingly:
| Trigger | How often | What |
|---|---|---|
| New review | every 30 minutes | new or changed review with text in one of your apps |
| Release status changed | every 30 minutes | new release in a track, different status or different rollout share |
| Vitals alert | every 3 hours | latest daily user-perceived crash or ANR rate above your threshold |
Each event starts the agent once. On their first run, "New review" and "Release status changed" only remember the current state and report nothing yet. The vitals alert reports at most once per app, metric and day, already on the first run.
Setup
1. Enable the APIs. In the Google Cloud Console, pick (or create) a project. Under APIs & Services → Library, search for Google Play Android Developer API and Google Play Developer Reporting API and click Enable for each.
2. Create a service account. Under IAM & Admin → Service accounts → Create service account, enter a name such as "Nema Crew". It needs no roles in the Cloud project. Then open the service account, Keys → Add key → Create new key → JSON. The JSON file is downloaded. It is a credential: do not share it or put it into a repository.
If your organisation cannot create keys, an organisation policy forbids it (iam.disableServiceAccountKeyCreation); a Google Cloud administrator then has to add an exception for the project.
3. Invite the service account in the Play Console. In the Play Console, under Users and permissions → Invite new users, enter the service account's email address (it ends in .iam.gserviceaccount.com and is also in the JSON file as client_email). Then choose the apps (or grant account permissions for all apps) and set the permissions:
| For the agent to … | the service account needs |
|---|---|
| read apps, releases, reviews and metrics | View app information and download bulk reports (read-only) – always required |
| reply to reviews | Reply to reviews |
| change release notes, rollouts and promotions in testing tracks | Release apps to testing tracks (or manage testing tracks) |
| do the same in production | Release to production, exclude devices, and use Play App Signing |
The module does not need financial data, orders or subscriptions. Only grant what you want to use.
4. Connect in Nema Crew. In the Nema Crew app, open Modules → Google Play and paste the whole content of the JSON file. Optional:
- Apps (package names): e.g.
com.example.app, com.example.other. Leave empty = all apps the service account can see (found through the Reporting API). - Crash rate alert (%) and ANR rate alert (%): thresholds for the vitals alert, default 1.09 and 0.47.
5. Save and test. Nema signs in to Google with the key and checks per app whether releases, reviews and metrics can be read. If something is missing, the test says exactly what: an API that is not enabled, a missing Play Console permission or an invalid key. Whether the service account may reply or change releases cannot be checked without a real change; if the permission is missing, the agent says so on the first attempt.
Be patient with new permissions. New permissions for a service account often do not apply at Google right away. Google gives no time frame; in practice it usually takes up to 24 hours, sometimes longer (providers of similar services report up to 36 hours). If the test reports a missing permission although it is set, test again later. Pasting the key again does not speed this up.
Limits of the Google APIs
- Reviews: The API only returns reviews with text that were written or changed in the last 7 days, and only for production. Star-only ratings, older reviews and testing feedback are only in the Play Console (or a CSV export). A reply has at most 350 characters, plain text. Google allows 200 reads per hour and 2,000 replies per day for each app.
- Metrics: Android vitals arrive with a delay of 1–2 days, as daily values in the Los Angeles time zone.
- Release notes: at most 500 characters per language.
- Rollouts: Google checks every change itself; it may reject a smaller rollout share than before, and the agent tells you. If your account uses managed publishing or an update was rejected, Google cannot send a change for review automatically; the agent then asks whether to save it without sending it for review, and you send it in the Play Console under Publishing overview.
- Changes are not visible at once: after committing, it can take a while until Google Play shows them.
If something does not work
| Message | What to do |
|---|---|
| API not enabled | Enable the named API in the service account's project in the Google Cloud Console, wait a few minutes, test again. |
| Permission missing | Grant the named permission for the app to the service account in the Play Console under Users and permissions; it can then take a while (see above). |
| Key rejected | The key was deleted or the service account disabled: create a new JSON key and paste it. |
| Not JSON / OAuth client | Use the key of a service account, not the client ID file. |
| Unknown app | Check the package name and grant the service account access to the app. |
| Quota reached | Google is limiting the requests; try again later. |
Data
Nema stores the key encrypted. It is only used to get an access token from Google and never appears in a log. The module does not store content from Google Play; it fetches it again for every task. For the triggers, Nema only remembers the last state (time of the newest review, status of the releases, date of the latest metrics) and identifiers of reported events. Details: privacy notice for the Google Play module.
Disconnect
In Nema Crew under Modules → Google Play → Disconnect. Nema then deletes the stored key. You delete the key itself at Google in the Google Cloud Console under IAM & Admin → Service accounts → Keys, and remove the permissions in the Play Console under Users and permissions. We recommend doing both.
Support
Questions and problems: support@nema.im.
Changes
- 1.0 · 5 November 2026 – First version: read apps, tracks and releases, reviews and Android vitals; reply to reviews, set release notes, steer rollouts and promote releases (each with a preview); triggers "New review", "Release status changed" and "Vitals alert".