Can HumDay connect to Google Play Game?

Yes. HumDay reads Google Play Game's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 31 operations are documented.

Do I need to write code to automate Google Play Game?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Play Game account.

What can HumDay do in Google Play Game?

10 of the 31 documented operations change something in Google Play Game, and 21 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Play Game account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Play Game is held behind that approval.

Automate Google Play Game

HumDay reads Google Play Game’s own published API description and derives 31 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Play Game is

The Google Play games service allows developers to enhance games with social leaderboards, achievements, game state, sign-in with Google, and more.

API host: games.googleapis.com

What HumDay can do in Google Play Game

10 documented operations change something in Google Play Game.

POSTRecords a batch of changes to the number of times events have occurred for the currently authenticated user of this application./games/v1/events
POSTIndicate that the currently authenticated user is playing your application./games/v1/applications/played
POSTSubmits multiple scores to leaderboards./games/v1/leaderboards/scores
POSTReturns a URL for the requested end point type./games/v1/applications/getEndPoint
POSTUpdates multiple achievements for the currently authenticated player./games/v1/achievements/updateMultiple
POSTSets the state of the achievement with the given ID to REVEALED for the currently authenticated player./games/v1/achievements/{achievementId}/reveal
POSTUnlocks this achievement for the currently authenticated player./games/v1/achievements/{achievementId}/unlock
POSTSubmits a score to the specified leaderboard./games/v1/leaderboards/{leaderboardId}/scores
POSTIncrements the steps of the achievement with the given ID for the currently authenticated player./games/v1/achievements/{achievementId}/increment
POSTSets the steps for the currently authenticated player towards unlocking an achievement./games/v1/achievements/{achievementId}/setStepsAtLeast

What HumDay can read from Google Play Game

These are the operations a schedule or a trigger can watch.

GETReturns a list showing the current progress on events in this application for the currently authenticated user./games/v1/events
GETReturns a list of the event definitions in this application./games/v1/eventDefinitions
GETReturns engagement and spend statistics in this application for the currently authenticated user./games/v1/stats
GETRetrieves scoped player identifiers for currently authenticated user./games/v1/players/me/scopedIds
GETLists all the achievement definitions for your application./games/v1/achievements
GETLists all the leaderboard metadata for your application./games/v1/leaderboards
GETReturn the metagame configuration data for the calling application./games/v1/metagameConfig
GETRetrieves a list of snapshots created by your application for the player corresponding to the player ID./games/v1/players/{playerId}/snapshots
GETChecks whether the games client is out of date./games/v1/revisions/check
GETGet the collection of players for the currently authenticated user./games/v1/players/me/players/{collection}
GETRetrieves the Player resource with the given ID./games/v1/players/{playerId}
GETRetrieves the metadata for a given snapshot ID./games/v1/snapshots/{snapshotId}
GETRetrieves the metadata of the application with the given ID./games/v1/applications/{applicationId}
GETRetrieves the metadata of the leaderboard with the given ID./games/v1/leaderboards/{leaderboardId}
GETList play data aggregated per category for the player corresponding to playerId./games/v1/players/{playerId}/categories/{collection}
GETGet the application player ids for the currently authenticated player across all requested games by the same developer as the calling application./games/v1/players/me/multipleApplicationPlayerIds
GETLists the progress for all your application's achievements for the currently authenticated player./games/v1/players/{playerId}/achievements
GETVerifies the auth token provided with this request is for the application with the specified ID, and returns the ID of the player it was granted for./games/v1/applications/{applicationId}/verify
GETLists the scores in a leaderboard, starting from the top./games/v1/leaderboards/{leaderboardId}/scores/{collection}
GETLists the scores in a leaderboard around (and including) a player's score./games/v1/leaderboards/{leaderboardId}/window/{collection}
GETGet high scores, and optionally ranks, in leaderboards for the currently authenticated player./games/v1/players/{playerId}/leaderboards/{leaderboardId}/scores/{timeSpan}

How automating Google Play Game works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Play Game account.
Grant access, then go live. You approve the specific Google Play Game operations it may use — and only those.