This section as Markdown: View Download

Google Play Integration

Connect your agent to the Google Play Developer API for review monitoring and app listing management.

Overview

The Google Play integration uses a Google Cloud service account with API access delegated from a Play Console project.

Skills that use this integration:

int-googleplay-reviews — Monitor and reply to Google Play reviews
int-googleplay-metadata — Read/update app listings and metadata
int-googleplay-events — Prepare assets and copy for Google Play promotional content (LiveOps events); reads only the app list

Agents that typically enable this integration:

App Review Support
Meta Ads Manager (uses the simpler apps array shape)
TikTok Ads Manager (uses the simpler apps array shape)

Availability

Mode	Status	Notes
Service Account JSON	Available	Google Cloud service account with Play Developer Reporting access.

Prerequisites

A Wiro API key — Authentication.
A deployed agent — Agent Overview.
A Google Play Console account with Admin access.
A Google Cloud project to host the service account.

Setup

Step 1: Enable the Google Play Android Developer API

Google Cloud Console → select project → APIs & Services → Library → Google Play Android Developer API → Enable.

Step 2: Create a service account

IAM & Admin → Service accounts → Create service account.
Name (e.g. "wiro-play-agent").
Grant role: Service Account Token Creator.
Skip user permissions → Done.
Open the service account → Keys → Add key → Create new key → JSON. Download.
Note the service account email from the account details page — format: [email protected].

Tip: In My Agents → open your agent → Credentials, upload the JSON and your service account email will appear with a Copy button.

Step 3: Link the service account to Play Console

Google Play Console → Users and permissions → Invite new users.
Email: the service account email ([email protected]).
Grant at least: View app information, Reply to reviews, and any others needed by your agent.
Send invite — Play Console auto-accepts for service accounts.

Step 4: Base64-encode the JSON

# Linux
base64 -w 0 play-service-account.json > play-sa.b64

# macOS
base64 -b 0 play-service-account.json > play-sa.b64

Step 5: Save to Wiro

The credential depends on which agent you're configuring. Review and metadata agents use google-play: the service account JSON plus a positional apps[] array. Each app entry carries appname + packagename. The promotional-content skill and the ads-manager agents need no service account: they read the app list from the separate google-play-apps credential, which holds only the apps[] array — send the same apps rows with "credentialkey": "google-play-apps".

curl -X POST "https://api.wiro.ai/v1/UserAgent/CredentialUpsert" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "fields": [
      { "credentialkey": "google-play", "fieldname": "serviceaccountjson", "fieldvalue": "eyJ0eXBlIjoic2VydmljZV9hY2NvdW50Ii..." },
      { "credentialkey": "google-play", "parentfield": "apps", "ordinal": 0, "fieldname": "appname",     "fieldvalue": "My App" },
      { "credentialkey": "google-play", "parentfield": "apps", "ordinal": 0, "fieldname": "packagename", "fieldvalue": "com.example.app" },
      { "credentialkey": "google-play", "parentfield": "apps", "ordinal": 1, "fieldname": "appname",     "fieldvalue": "Pro Version" },
      { "credentialkey": "google-play", "parentfield": "apps", "ordinal": 1, "fieldname": "packagename", "fieldvalue": "com.example.other" }
    ]
  }'

For multiple apps, append more apps-prefixed ordinal rows. Positional merge applies — sending no apps rows leaves the existing list untouched; to clear the list, send { "credentialkey": "google-play", "fieldname": "apps", "fieldvalue": [] }.

Reply skills can also use a global support email. It is optional: without it, reply drafts leave out the contact line. Set it once via the dedicated var-support-email credential (shared across int-appstore-reviews and int-googleplay-reviews):

curl -X POST "https://api.wiro.ai/v1/UserAgent/CredentialUpsert" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "useragentguid": "your-useragent-guid",
    "fields": [
      { "credentialkey": "var-support-email", "fieldname": "value", "fieldvalue": "[email protected]" }
    ]
  }'

Field	Type	Required	Description
`serviceaccountjson`	string	Yes	Base64-encoded service account JSON. Stored encrypted-at-rest in the DB (`type: fileinput-base64`).
`apps[].appname`	string	Yes	Friendly label the agent uses when reporting back ("scanned reviews on My Android App").
`apps[].packagename`	string	Yes	Android package name (e.g. `com.example.app`).
`var-support-email.value`	string	No	Global support email — surfaced when reviewers are pointed to direct contact. Lives on the dedicated `var-support-email` credential, not on `google-play`.

Step 6: Start the agent

curl -X POST "https://api.wiro.ai/v1/UserAgent/Start" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{ "guid": "your-useragent-guid" }'

Runtime Behavior

Wiro mints an OAuth access token from the service account JSON on demand and calls Google Play at https://androidpublisher.googleapis.com/androidpublisher/v3/... with Authorization: Bearer <TOKEN>. The apps[] list scopes which package names the agent operates on.

Troubleshooting

403 "The caller does not have permission": Service account is in Google Cloud but hasn't been invited in Play Console, or lacks the required permission. Return to Play Console → Users and permissions and adjust.
"Invalid JWT token": Service account JSON corrupt or truncated. Re-encode.
Review reply fails silently: Some reviews are >1 year old and can't be replied to via API — Google enforces this at the platform level.