Can HumDay connect to Google Firebase Hosting?

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

Do I need to write code to automate Google Firebase Hosting?

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

What can HumDay do in Google Firebase Hosting?

10 of the 17 documented operations change something in Google Firebase Hosting, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Firebase Hosting

HumDay reads Google Firebase Hosting’s own published API description and derives 17 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 Firebase Hosting is

The Firebase Hosting REST API enables programmatic and customizable management and deployments to your Firebase-hosted sites. Use this REST API to create and manage channels and sites as well as to deploy new or updated hosting configurations and content files.

API host: firebasehosting.googleapis.com

What HumDay can do in Google Firebase Hosting

10 documented operations change something in Google Firebase Hosting.

POSTCreates a new channel in the specified site./v1beta1/{parent}/channels
POSTAdds content files to the specified version./v1beta1/{parent}:populateFiles
POSTCreates a new Hosting Site in the specified parent Firebase project./v1beta1/{parent}/sites
POSTCreates a new release, which makes the content of the specified version actively display on the appropriate URL(s)./v1beta1/{parent}/releases
POSTCreates a new version for the specified site./v1beta1/{parent}/versions
POSTCreates a new version on the specified target site using the content of the specified version./v1beta1/{parent}/versions:clone
POSTCreates a domain mapping on the specified site./v1beta1/{parent}/domains
DELETEDeletes the specified version./v1beta1/{name}
PATCHUpdates the specified metadata for the specified version./v1beta1/{name}
PUTUpdates the specified domain mapping, creating the mapping as if it does not exist./v1beta1/{name}

What HumDay can read from Google Firebase Hosting

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

GETLists the remaining files to be uploaded for the specified version./v1beta1/{parent}/files
GETLists the channels for the specified site./v1beta1/{parent}/channels
GETLists the releases that have been created for the specified site or channel./v1beta1/{parent}/releases
GETGet the specified version that has been created for the specified site./v1beta1/{name}
GETLists each Hosting Site associated with the specified parent Firebase project./v1beta1/{parent}/sites
GETLists the domains for the specified site./v1beta1/{parent}/domains
GETLists the versions that have been created for the specified site./v1beta1/{parent}/versions

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