Short answer: You can update google contact in Google Contacts by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Google Contacts Update Google Contact action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Resource Name resource_name | string | Required | The resource name of the contact to update, e.g. 'people/c123456789' |
ETag etag | string | Required | The etag from the contact's current data (required for conflict detection) |
First Name givenName | string | Optional | The contact's first name |
Last Name familyName | string | Optional | The contact's last name |
Email Address email | string | Optional | The contact's email address |
Phone Number phone | string | Optional | The contact's phone number |
{"resource_name": "e.g. people/c123456789","etag": "e.g. %EgUBAi43PRoEAQIFBw==","givenName": "e.g. John","familyName": "e.g. Doe","email": "e.g. john.doe@example.com"}
{"etag": "%EgUBAi43PRoEBQIFBw==","names": [{"givenName": "John","familyName": "Smith","displayName": "John Smith"}],"phoneNumbers": [{"value": "+1-555-987-6543"}],"resourceName": "people/c123456789","emailAddresses": [{"value": "john.smith@example.com"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.