Can HumDay connect to Google Proximity Beacon?

Yes. HumDay reads Google Proximity Beacon'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 Proximity Beacon?

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 Proximity Beacon account.

What can HumDay do in Google Proximity Beacon?

11 of the 17 documented operations change something in Google Proximity Beacon, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Proximity Beacon

HumDay reads Google Proximity Beacon’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 Proximity Beacon is

Registers, manages, indexes, and searches beacons.

API host: proximitybeacon.googleapis.com

What HumDay can do in Google Proximity Beacon

11 documented operations change something in Google Proximity Beacon.

POSTRegisters a previously unregistered beacon given its advertisedId./v1beta1/beacons:register
POSTGiven one or more beacon observations, returns any beacon information and attachments accessible to your application./v1beta1/beaconinfo:getforobserved
DELETEDeletes the specified beacon including all diagnostics data for the beacon as well as any attachments on the beacon (including those belonging to other projects)./v1beta1/{beaconName}
PUTUpdates the information about the specified beacon./v1beta1/{beaconName}
PUTUpdates the information about the specified namespace./v1beta1/{namespaceName}
DELETEDeletes the specified attachment for the given beacon./v1beta1/{attachmentName}
POSTActivates a beacon. A beacon that is active will return information and attachment data when queried via beaconinfo.getforobserved. Calling this method on an already active beacon…/v1beta1/{beaconName}:activate
POSTDeactivates a beacon. Once deactivated, the API will not return information nor attachment data for the beacon when queried via beaconinfo.getforobserved. Calling this method on a…/v1beta1/{beaconName}:deactivate
POSTDecommissions the specified beacon in the service./v1beta1/{beaconName}:decommission
POSTAssociates the given data with the specified beacon./v1beta1/{beaconName}/attachments
POSTDeletes multiple attachments on a given beacon./v1beta1/{beaconName}/attachments:batchDelete

What HumDay can read from Google Proximity Beacon

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

GETSearches the beacon registry for beacons that match the given search criteria./v1beta1/beacons
GETList the diagnostics for a single beacon./v1beta1/{beaconName}/diagnostics
GETGets the Proximity Beacon API's current public key and associated parameters used to initiate the Diffie-Hellman key exchange required to register a beacon that broadcasts the Edd…/v1beta1/eidparams
GETLists all attachment namespaces owned by your Google Developers Console project./v1beta1/namespaces
GETReturns detailed information about the specified beacon./v1beta1/{beaconName}
GETReturns the attachments for the specified beacon that match the specified namespaced-type pattern./v1beta1/{beaconName}/attachments

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