Can HumDay connect to Google Cloud IoT?

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

Do I need to write code to automate Google Cloud IoT?

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 Cloud IoT account.

What can HumDay do in Google Cloud IoT?

11 of the 16 documented operations change something in Google Cloud IoT, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Cloud IoT

HumDay reads Google Cloud IoT’s own published API description and derives 16 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 Cloud IoT is

Registers and manages IoT (Internet of Things) devices that connect to the Google Cloud Platform.

API host: cloudiot.googleapis.com

What HumDay can do in Google Cloud IoT

11 documented operations change something in Google Cloud IoT.

POSTSends a command to the specified device./v1/{name}:sendCommandToDevice
POSTCreates a device in a device registry./v1/{parent}/devices
POSTCreates a device registry that contains devices./v1/{parent}/registries
DELETEDeletes a device./v1/{name}
PATCHUpdates a device./v1/{name}
POSTGets the access control policy for a resource./v1/{resource}:getIamPolicy
POSTSets the access control policy on the specified resource./v1/{resource}:setIamPolicy
POSTAssociates the device with the gateway./v1/{parent}:bindDeviceToGateway
POSTReturns permissions that a caller has on the specified resource./v1/{resource}:testIamPermissions
POSTModifies the configuration for the device, which is eventually sent from the Cloud IoT Core servers./v1/{name}:modifyCloudToDeviceConfig
POSTDeletes the association between the device and the gateway./v1/{parent}:unbindDeviceFromGateway

What HumDay can read from Google Cloud IoT

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

GETLists the last few versions of the device state in descending order (i.e.: newest first)./v1/{name}/states
GETList devices in a device registry./v1/{parent}/devices
GETLists the last few versions of the device configuration in descending order (i.e.: newest first)./v1/{name}/configVersions
GETGets details about a device./v1/{name}
GETLists device registries./v1/{parent}/registries

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