Can HumDay connect to Google Play Game Publishing?

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

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

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 Publishing account.

What can HumDay do in Google Play Game Publishing?

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

Is my Google Play Game Publishing 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 Publishing is held behind that approval.

Automate Google Play Game Publishing

HumDay reads Google Play Game Publishing’s own published API description and derives 10 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 Publishing is

The Google Play Game Services Publishing API allows developers to configure their games in Game Services.

API host: gamesconfiguration.googleapis.com

What HumDay can do in Google Play Game Publishing

6 documented operations change something in Google Play Game Publishing.

POSTInsert a new achievement configuration in this application./games/v1configuration/applications/{applicationId}/achievements
POSTInsert a new leaderboard configuration in this application./games/v1configuration/applications/{applicationId}/leaderboards
DELETEDelete the achievement configuration with the given ID./games/v1configuration/achievements/{achievementId}
PUTUpdate the metadata of the achievement configuration with the given ID./games/v1configuration/achievements/{achievementId}
DELETEDelete the leaderboard configuration with the given ID./games/v1configuration/leaderboards/{leaderboardId}
PUTUpdate the metadata of the leaderboard configuration with the given ID./games/v1configuration/leaderboards/{leaderboardId}

What HumDay can read from Google Play Game Publishing

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

GETReturns a list of the achievement configurations in this application./games/v1configuration/applications/{applicationId}/achievements
GETReturns a list of the leaderboard configurations in this application./games/v1configuration/applications/{applicationId}/leaderboards
GETRetrieves the metadata of the achievement configuration with the given ID./games/v1configuration/achievements/{achievementId}
GETRetrieves the metadata of the leaderboard configuration with the given ID./games/v1configuration/leaderboards/{leaderboardId}

How automating Google Play Game Publishing 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 Publishing account.
Grant access, then go live. You approve the specific Google Play Game Publishing operations it may use — and only those.