Read and manage contacts through a named Google account.
Explore 8 workflow actions for Google Contacts, including account permissions and operation limits.
5 read actions3 write actions
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Continue contact sync page
Read
Continue a full or incremental contact sync with Google's opaque next page token.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/contacts
Operation limits
Use the same page size and field selection as the first sync request. When continuing an incremental sync, also send the same sync token used to start it. Only the final page contains nextSyncToken. Treat page and sync tokens as opaque and store them in workflow state.
Pagination: cursor. Check the result for additional pages; a single action may not return every record.
Create contact
Write
Create a contact with a name, email address or phone number.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/contacts
Operation limits
Google recommends sequential contact mutations for one account. A write is sent once; a lost reply leaves the workflow uncertain without an automatic resend.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Delete contact
Write
Delete a contact's CONTACT data by person ID.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/contacts
Operation limits
Google deletes contact data, not other profile data. Confirm the selected person ID before running this action.
Google recommends sequential contact mutations for one account. A write is sent once; a lost reply leaves the workflow uncertain without an automatic resend.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Get contact
Read
Read a contact by its Google person ID.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/contacts
Get many contacts
Read
Read up to 50 known contacts by their full Google resource names.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/contacts
Operation limits
Returns only the named contacts, up to 50 per call. A response can contain a per-person error instead of a Person. Use the returned requestedResourceName and status to reconcile each result.
List contacts
Read
Read one page of the connected account's contacts.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/contacts
Pagination: cursor. Check the result for additional pages; a single action may not return every record.
Start or resume contact sync
Read
Start a full contact sync or use a saved sync token to read changes since the previous completed sync.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/contacts
Operation limits
Sync tokens expire seven days after the full sync. If Google reports EXPIRED_SYNC_TOKEN, start a new full sync without a sync token. Deleted contacts in incremental results have metadata.deleted set to true. Writes can take several minutes to appear in sync results.
Pagination: cursor. Check the result for additional pages; a single action may not return every record.
Update contact
Write
Replace selected contact fields using the current CONTACT source etag.
Permissions and limits
Account permissions
https://www.googleapis.com/auth/contacts
Operation limits
The Person resourceName must match the selected contact ID. Each field in updatePersonFields replaces that whole field, so include every value to retain. Get contact first and use its current CONTACT source ID and etag.
Google recommends sequential contact mutations for one account. A write is sent once; a lost reply leaves the workflow uncertain without an automatic resend.
A repeated request may repeat the external action. Review the previous result before retrying a write.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in Google Contacts. A saved workflow is not a completed provider action.
