Can HumDay connect to Google Android Device Provisioning Partner?

Yes. HumDay reads Google Android Device Provisioning Partner's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 23 operations are documented.

Do I need to write code to automate Google Android Device Provisioning Partner?

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 Android Device Provisioning Partner account.

What can HumDay do in Google Android Device Provisioning Partner?

15 of the 23 documented operations change something in Google Android Device Provisioning Partner, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Android Device Provisioning Partner 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 Android Device Provisioning Partner is held behind that approval.

Automate Google Android Device Provisioning Partner

HumDay reads Google Android Device Provisioning Partner’s own published API description and derives 23 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 Android Device Provisioning Partner is

Automates Android zero-touch enrollment for device resellers, customers, and EMMs.

API host: androiddeviceprovisioning.googleapis.com

What HumDay can do in Google Android Device Provisioning Partner

15 documented operations change something in Google Android Device Provisioning Partner.

POSTCreates a customer for zero-touch enrollment./v1/{parent}/customers
POSTCreates a new configuration./v1/{parent}/configurations
POSTUnclaims a device from a customer and removes it from zero-touch enrollment./v1/{parent}/devices:unclaim
DELETEDeletes an unused configuration./v1/{name}
PATCHUpdates a configuration's field values./v1/{name}
POSTClaims a device for a customer and adds it to zero-touch enrollment./v1/partners/{partnerId}/devices:claim
POSTApplies a Configuration to the device to register the device for zero-touch enrollment./v1/{parent}/devices:applyConfiguration
POSTRemoves a configuration from device./v1/{parent}/devices:removeConfiguration
POSTUnclaims a device from a customer and removes it from zero-touch enrollment./v1/partners/{partnerId}/devices:unclaim
POSTClaims a batch of devices for a customer asynchronously./v1/partners/{partnerId}/devices:claimAsync
POSTFinds devices claimed for customers./v1/partners/{partnerId}/devices:findByOwner
POSTUnclaims a batch of devices for a customer asynchronously./v1/partners/{partnerId}/devices:unclaimAsync
POSTFinds devices by hardware identifiers, such as IMEI./v1/partners/{partnerId}/devices:findByIdentifier
POSTUpdates the reseller metadata attached to a batch of devices./v1/partners/{partnerId}/devices:updateMetadataAsync
POSTUpdates reseller metadata associated with the device./v1/partners/{metadataOwnerId}/devices/{deviceId}/metadata

What HumDay can read from Google Android Device Provisioning Partner

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

GETLists the user's customer accounts./v1/customers
GETLists a customer's devices./v1/{parent}/devices
GETLists a customer's configurations./v1/{parent}/configurations
GETLists the DPCs (device policy controllers) that support zero-touch enrollment./v1/{parent}/dpcs
GETLists the customers of the vendor./v1/{parent}/customers
GETGets a device./v1/{name}
GETLists the customers that are enrolled to the reseller identified by the partnerId argument./v1/partners/{partnerId}/customers
GETLists the vendors of the partner./v1/{parent}/vendors

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