List Contacts
🧾 Definition
The "List Contacts" action in the Google Workspace category allows you to retrieve all contacts saved in a specified user’s Google Contacts account. This includes detailed information such as display names, phone numbers, email addresses, and resource identifiers. It's designed to help administrators, HR teams, or workflow builders extract and utilize contact data for audits, reporting, synchronization, or automated communication processes. By using this action, you can seamlessly access and process personal or professional contact lists as part of a broader workflow in Zenphi.
📌 Example Use Cases
Contact Backup Automation
Automatically export and back up a user's contact list to a Google Sheet or external system on a scheduled basis.
HR Onboarding Audit
Ensure new employees have a pre-configured set of contacts by comparing their Google Contacts list to a standard template.
CRM Synchronization
Sync Google Contacts data with a third-party CRM system to keep customer records up to date across platforms.
Data Compliance and Review
Periodically retrieve and review contact lists to verify that sensitive or unauthorized entries are not stored.
Communication Flows
Use retrieved contact details to trigger automated emails, messages, or notifications in workflow automations.
🔽 Inputs
Connection
A required Google Workspace Administration connection.To use this action, you must upload a Google service account credential JSON file with domain-wide delegation enabled. This setup allows Zenphi to securely act on behalf of users and access their Google Contacts data. 👉 How to create this connection
User Email
Enter the primary email address of the user whose contact list you wish to retrieve.This field tells Zenphi which user’s Google Contacts to access. Make sure the specified email belongs to a valid user in your Google Workspace domain and the service account has the necessary permissions to access that user's contact data.
📤 Outputs
When the "List Contacts" action is executed, it returns a structured list of the user's Google Contacts, providing detailed and organized information for each contact entry. Below is a breakdown of each output field:
Resource Name
A unique, system-generated identifier for each contact.This ID is used internally by Google Contacts and can be helpful when referencing, updating, or deleting specific contacts programmatically.
Display Name
The full name of the contact, formatted based on the viewer’s locale preferences.It gives a user-friendly representation of the contact, making it easier to recognize at a glance.
First Name
The contact’s given name.Useful for personalizing communications or filtering contacts alphabetically by first name.
Last Name
The contact’s family or surname.Helpful for sorting, indexing, or when performing more formal communications and recordkeeping.
Contact Numbers
A list containing the phone numbers associated with the contact. Each number includes:
- Contact Number: The actual phone number.
- Type: The label for the number (e.g., mobile, work, home).
This helps distinguish between personal and professional contact details for each person.
Email Addresses
A list containing the email addresses linked to the contact. Each email entry includes:
- Email: The email address itself.
- Type: The category of the email (e.g., work, home, other).
This is essential for identifying the correct channel for communication depending on context.
📘 Example Scenario: Syncing User Contacts to a CRM System
An IT administrator at a mid-sized company wants to ensure that the sales team’s Google Contacts are regularly synced with the company’s CRM system. To automate this process, they create a Zenphi flow that uses the "List Contacts" action.
In the flow setup:
- The admin adds a Google Workspace Administration connection using a service account with domain-wide delegation.
- They provide the User Email of a specific salesperson (e.g.,
[email protected]
) whose contacts need to be retrieved. - The "List Contacts" action pulls all available contacts, including names, phone numbers, and email addresses.
- A subsequent action formats and sends this data to the CRM system via API or writes it to a shared Google Sheet.
This setup ensures that the CRM always reflects the most current contact information without manual data entry, helping the sales team stay productive and organized.
Updated about 17 hours ago