Can HumDay connect to Google Firebase App Distribution?

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

Do I need to write code to automate Google Firebase App Distribution?

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 Firebase App Distribution account.

What can HumDay do in Google Firebase App Distribution?

12 of the 18 documented operations change something in Google Firebase App Distribution, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Firebase App Distribution 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 Firebase App Distribution is held behind that approval.

Automate Google Firebase App Distribution

HumDay reads Google Firebase App Distribution’s own published API description and derives 18 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 HumDay can do in Google Firebase App Distribution

12 documented operations change something in Google Firebase App Distribution.

POSTUploads a binary. Uploading a binary can result in a new release being created, an update to an existing release, or a no-op if a release with the same binary already exists./v1/{app}/releases:upload
POSTBatch adds testers. This call adds testers for the specified emails if they don't already exist. Returns all testers specified in the request, including newly created and previous…/v1/{project}/testers:batchAdd
POSTBatch adds members to a group./v1/{group}:batchJoin
POSTCreate a group./v1/{parent}/groups
DELETEDelete a group./v1/{name}
PATCHUpdate a tester. If the testers joins a group they gain access to all releases that the group has access to./v1/{name}
POSTWaits until the specified long-running operation is done or reaches at most a specified timeout, returning the latest state./v1/{name}:wait
POSTStarts asynchronous cancellation on a long-running operation./v1/{name}:cancel
POSTDistributes a release to testers./v1/{name}:distribute
POSTBatch removed members from a group./v1/{group}:batchLeave
POSTDeletes releases. A maximum of 100 releases can be deleted per request./v1/{parent}/releases:batchDelete
POSTBatch removes testers./v1/{project}/testers:batchRemove

What HumDay can read from Google Firebase App Distribution

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

GETList groups./v1/{parent}/groups
GETLists releases. By default, sorts by createTime in descending order./v1/{parent}/releases
GETGet a group./v1/{name}
GETLists testers and their resource ids./v1/{parent}/testers
GETLists operations that match the specified filter in the request./v1/{name}/operations
GETLists feedback reports./v1/{parent}/feedbackReports

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