Automate Google Mirror

What Google Mirror is

Interacts with Glass users via the timeline.

API host: www.googleapis.com

What HumDay can do in Google Mirror

14 documented operations change something in Google Mirror.

• POSTInserts a new contact./contacts
• POSTCreates a new subscription./subscriptions
• POSTInserts a new item into the timeline./timeline
• POSTAdds a new attachment to a timeline item./timeline/{itemId}/attachments
• DELETEDeletes a contact./contacts/{id}
• PATCHUpdates a contact in place./contacts/{id}
• PUTUpdates a contact in place./contacts/{id}
• DELETEDeletes a timeline item./timeline/{id}
• PATCHUpdates a timeline item in place./timeline/{id}
• PUTUpdates a timeline item in place./timeline/{id}
• DELETEDeletes a subscription./subscriptions/{id}
• PUTUpdates an existing subscription in place./subscriptions/{id}
• POSTInserts a new account for a user/accounts/{userToken}/{accountType}/{accountName}
• DELETEDeletes an attachment from a timeline item./timeline/{itemId}/attachments/{attachmentId}

What HumDay can read from Google Mirror

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

• GETRetrieves a list of contacts for the authenticated user./contacts
• GETRetrieves a list of timeline items for the authenticated user./timeline
• GETRetrieves a list of locations for the user./locations
• GETRetrieves a list of subscriptions for the authenticated user and service./subscriptions
• GETGets a single contact by ID./contacts/{id}
• GETReturns a list of attachments for a timeline item./timeline/{itemId}/attachments
• GETGets a single timeline item by ID./timeline/{id}
• GETGets a single setting by ID./settings/{id}
• GETGets a single location by ID./locations/{id}
• GETRetrieves an attachment on a timeline item by item ID and attachment ID./timeline/{itemId}/attachments/{attachmentId}

How automating Google Mirror works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. 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.
3. See it proven. The program runs and shows you the result before it is allowed near your live Google Mirror account.
4. Grant access, then go live. You approve the specific Google Mirror operations it may use — and only those.

Automate Google Mirror with these

• Gmail79 operations
• Google+9 operations
• Google Abusive Experience Report2 operations
• Google Accelerated Mobile Pages (AMP) URL1 operations
• Google Access Approval7 operations
• Google Access Context Manager9 operations
• Google ACME DNS2 operations
• Google Ad Exchange Buyer38 operations
• Google Ad Exchange Buyer II50 operations
• Google Ad Experience Report2 operations
• Google Admin SDK122 operations
• Google AdMob7 operations

Questions about Google Mirror automation

Can HumDay connect to Google Mirror?

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

Do I need to write code to automate Google Mirror?

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

What can HumDay do in Google Mirror?

14 of the 24 documented operations change something in Google Mirror, and 10 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Where this came from

The operations above are read from a published API description for Google Mirror at www.googleapis.com/discovery/v1/apis/mirror/v1/rest. Descriptions are the provider’s own words, not ours. Last published 2020-01-07.