Short answer: Drop the "Google Contacts → List Google Contacts" 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 |
|---|---|---|---|
Page Size pageSize | string | Optional | Maximum number of contacts to return (max 1000) |
Page Token pageToken | string | Optional | Token for pagination, from a previous response's nextPageToken |
{"pageSize": "100","pageToken": "e.g. CAoQAA"}
{"totalItems": 150,"connections": [{"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"}]}],"totalPeople": 150,"nextPageToken": "CAoQAA"}
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.