Short answer: Drop the "Google Contacts → Create 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 |
|---|---|---|---|
First Name givenName | string | Required | 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 |
{"givenName": "e.g. John","familyName": "e.g. Doe","email": "e.g. john.doe@example.com","phone": "e.g. +1-555-123-4567"}
{"etag": "%EgUBAi43PRoEAQIFBw==","names": [{"givenName": "John","familyName": "Doe","displayName": "John Doe"}],"phoneNumbers": [{"value": "+1-555-123-4567"}],"resourceName": "people/c987654321","emailAddresses": [{"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.