Gets a single contact by ID in Google Mirror
A documented Google Mirror operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Gets a single contact by ID.
- GETReads data · contacts
www.googleapis.com/contacts/{id}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Google Mirror operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Google Mirror operations
- Inserts a new contactPOST · changes data
- Creates a new subscriptionPOST · changes data
- Inserts a new item into the timelinePOST · changes data
- Adds a new attachment to a timeline itemPOST · changes data
- Deletes a contactDELETE · changes data
- Updates a contact in placePATCH · changes data
- Updates a contact in placePUT · changes data
- Deletes a timeline itemDELETE · changes data
Questions
- Can HumDay gets a single contact by id in Google Mirror?
- Yes. This operation is published in Google Mirror's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Google Mirror account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Google Mirror.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Mirror account.
Where this came from
Read from a published API description for Google Mirror at www.googleapis.com/discovery/v1/apis/mirror/v1/rest. The description above is the provider’s own wording, not ours. Last published 2020-01-07.