Definition

The “Find Customer” action in Google Reseller allows you to retrieve comprehensive information about a specific customer within your Google Workspace reseller account.

Key capabilities:

• Retrieve detailed customer profiles using their unique identifier or primary domain name.
• Access critical contact information, including primary admin details, phone numbers, and postal addresses.
• Verify customer domain status and customer type (domain-verified or email-verified).

This action streamlines customer management by allowing you to automatically pull up-to-date client details into your workflows for reporting, billing, or automated communications.

Inputs

1. Connection: This field is used to securely connect Zenphi to your Google Reseller account.

• Practical Guidance: You can select a pre-configured connection from the dropdown menu, or create a new one by authenticating with your Google credentials. This is typically a static selection that remains the same every time the workflow runs.
• Use Case Context: You would use the “Connection” field to authorize Zenphi so it has the necessary permissions to search for customers in your specific reseller account.

2. Customer id: This field is used to specify exactly which customer’s information you want to retrieve, using either their primary domain name or their unique Google customer identifier.

• Practical Guidance: You can type a specific domain name (e.g., “company.com”) directly into the field as a static value if you always want to look up the same customer. More commonly, you will use a dynamic value from the token picker (the chain icon) to pass in a customer ID or domain name from a previous step, such as a trigger from a new support ticket or a form submission.
• Use Case Context: You would use the “Customer id” field to tell Zenphi exactly which client’s profile needs to be fetched for the current workflow run.

Outputs

1. Customer object: This output provides a comprehensive collection of data about the specified customer, including their domain, contact details, and address.

• Utility: This object and its nested properties are highly valuable for subsequent steps in your automation. For example, you can use the “Primary email” to send an automated onboarding email, or pass the “Postal Address” details into a document generation step to create a customized invoice or contract.
  • Customer Id: The unique identifier for the customer. Useful for passing into subsequent Google Reseller or Google Workspace actions that require a specific customer ID to apply changes or assign licenses.
  • Customer Domain: The customer’s primary domain name string. You can use this in a later step to verify domain-specific settings or route notifications to the correct domain administrator.
  • Customer Type: Identifies if the customer is domain-verified (domain) or email-verified (team). This is useful in a “Condition” (If/Else) step to route workflows differently based on the customer’s verification status.
  • Primary Admin: An object containing the first admin details of the customer (present for TEAM customers).
    • Primary email: The business email of the primary administrator. You can use this token in a “Send Email” action to directly contact the customer’s main administrator with important updates.
  • Alternate Email: Provides the alternate email address associated with the account. This can be used as a backup contact method in a “Send Email” step if the primary admin is unreachable.
  • Resource Ui Url: The URL to the customer’s Subscriptions page in the Google Admin console. You can include this link in a Slack message or email to your internal team, allowing them to instantly click and view the customer’s subscriptions.
  • Customer Domain Verified: A true/false (boolean) value indicating if the domain is verified. Highly useful in an “If Condition” step to automatically send a reminder email to customers who have not yet verified their domain.
  • Phone Number: The customer’s contact phone number. This can be passed into an SMS action to send automated text alerts, or logged directly into your CRM.
  • Postal Address: An object containing the customer’s detailed address information.
    • Organization Name: The name of the customer’s organization. Useful for personalizing emails or generating official documents.
    • Contact Name: The designated contact person’s name. Can be used to personalize the greeting in automated communications.
    • Region: The region or state. Useful for routing the customer to a specific regional sales representative.
    • Country Code: The country code. Useful for conditional routing or formatting international phone numbers in later steps.
    • Locality: The city or locality. Can be used for geographic reporting or segmenting customers.
    • Address Line 1: The first line of the address. Essential for generating accurate invoices or shipping documents via document generation actions.
    • Address Line 2: The second line of the address. Useful for ensuring complete shipping or billing details.
    • Address Line 3: The third line of the address. Additional address line if required for international or complex shipping addresses.
    • Postal Code: The postal or zip code. Useful for validating addresses or territory mapping in subsequent CRM steps.

Example Use Cases

1. Automate Invoice Generation Retrieve a customer’s postal address and organization name to automatically populate and generate billing documents.
2. Enrich Support Tickets Fetch detailed customer information dynamically when a new support request is received to provide agents with immediate context.
3. Audit Domain Verification Check the verification status of a customer’s domain and automatically route unverified accounts to a follow-up sequence.
4. Streamline Client Onboarding Pull the primary admin’s contact details and company information to automatically send personalized welcome emails and setup instructions.

Example

Scenario: As a Google Workspace reseller, you need to automatically generate an accurate, customized service agreement whenever an existing client requests a subscription upgrade. Instead of manually looking up the client’s billing address and primary admin details in the Google Admin console, you want to automatically fetch this data and merge it into a contract template.

Steps to Implement:

1. Set the Trigger
   • Choose “Zenphi Form” as the trigger to capture the client’s upgrade request, ensuring you include a field for their domain name.
2. Configure the “Find Customer” Action
   • Add the “Find Customer” action to your flow.
   • Connection: Select your authorized Google Reseller connection from the dropdown.
   • Customer id: Use the token picker (chain icon) to dynamically insert the domain name provided by the client in the Zenphi Form trigger.
3. Generate the Contract
   • Add a document generation action (e.g., Generate Document using Google Docs).
   • Map the outputs from the “Find Customer” action (such as Organization Name, Address Line 1, Locality, and Postal Code) into your document template.
4. Send the Agreement
   • Add a “Send Email” action, using the “Primary email” output from the “Find Customer” action as the recipient address to deliver the generated contract directly to the customer’s administrator.

Outcome: The workflow automatically retrieves the exact customer details needed to generate and send a legally accurate service agreement. This eliminates manual data entry errors, significantly speeds up the upgrade process, and ensures your team can handle client requests efficiently without navigating away from their primary workspace.

Best Practices

1. Use Dynamic Customer IDs Instead of hardcoding a domain name, use the token picker to pass the Customer ID or domain dynamically from a previous trigger or action to make your workflow scalable across all clients.
2. Verify Domain Status Utilize the “Customer Domain Verified” output in an “If Condition” step to ensure you only provision services or send critical communications to fully verified accounts.
3. Implement Fallback Contacts When configuring automated emails, use the “Alternate Email” output as a backup or CC address in case the “Primary email” administrator is unavailable or unresponsive.
4. Protect Customer Data Since this action retrieves sensitive Personally Identifiable Information (PII) like phone numbers and postal addresses, ensure this data is only passed into secure, authorized downstream actions like CRM updates or official document generation.