Short answer: Drop the "Google Contacts → Get Google Contact" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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, e.g. 'people/c123456789' |
{"resource_name": "e.g. people/c123456789"}
{"etag": "%EgUBAi43PRoEAQIFBw==","names": [{"givenName": "John","familyName": "Doe","displayName": "John Doe"}],"phoneNumbers": [{"type": "mobile","value": "+1-555-123-4567"}],"resourceName": "people/c123456789","organizations": [{"name": "Acme Corp","title": "Software Engineer"}],"emailAddresses": [{"type": "work","value": "john.doe@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.
Triggered by anything in the catalog. Free tier available. No credit card.