🧾 Definition

The "List Gmail Signatures" action in the Google Workspace category allows administrators to retrieve all email signatures configured for a specified user's Gmail account. This includes details such as the email aliases, associated display names, reply-to addresses, HTML signature content, and whether the alias is set as default. This action is especially useful for auditing and managing user signature configurations across your organization, ensuring consistency in branding, contact info, and compliance.

💼 Example Use Cases

Audit Email Branding Consistency

Retrieve and review user signatures across the organization to ensure they comply with company branding and formatting standards.

Pre-Migration Verification

Before migrating Gmail accounts or modifying signature policies, list current signatures to back them up or analyze changes.

Support Troubleshooting

Help desk teams can quickly verify if a user's signature is properly configured when users report missing or incorrect email signatures.

Automated Signature Compliance Check

Use in automated workflows to periodically check for blank or outdated signatures and notify the user or IT admin.

Onboarding/Offboarding Review

Review a user’s email signature setup during onboarding to ensure correct contact details, or before offboarding to log any personalized content.

🛠️ Inputs

Connection

A required Google Workspace Administration connection.To authenticate and authorize this action, you must upload a Google service account credential JSON file with domain-wide delegation enabled. This allows Zenphi to act on behalf of users in your organization and access their Gmail settings securely.👉 How to create this connection

User Email

The primary email address of the user whose Gmail signatures you want to retrieve.This should be a valid and existing user within your Google Workspace domain. Zenphi uses this email to locate and access the user’s Gmail signature settings via the Admin SDK and Gmail API.

📤 Outputs

This action returns a list of Gmail signatures associated with the specified user's email address. Each signature entry contains the following details:

Send As Email

The email address used in the ‘From’ field when sending emails with this alias.This indicates the identity the message appears to come from, which may include the user’s primary or secondary (alias) addresses.

Display Name

The name shown in the ‘From’ field alongside the email address.This is typically the sender’s full name or a team name and is visible to recipients in their inbox, improving personalization or branding.

Reply-To Address

An optional email address that appears in the ‘Reply-To’ header.If set, replies to emails sent from this alias will go to this address instead of the original sender address. Useful for forwarding replies to a shared inbox or different contact.

Signature

The HTML-formatted email signature configured for the alias.This content is automatically appended to outgoing messages when composing emails in the Gmail web interface, and may include text, links, company logos, or legal disclaimers.

Is Default

Indicates whether this alias is set as the default ‘From’ address.When set to true, Gmail will use this address by default when the user starts a new message or triggers automated replies like vacation responders.

📘 Example Scenario: Auditing Employee Email Signatures for Branding Consistency

A company’s IT administrator is tasked with ensuring that all employees use a standardized email signature that includes the company logo, job title, and contact information. To streamline this audit, the admin sets up a Zenphi flow using the “List Gmail Signatures” action.

They configure the action with:

A Google Workspace Administration connection using a service account with domain-wide delegation.
The email address of the target user whose signature they want to retrieve.

Once the flow runs, it returns all signature configurations linked to that user, including any aliases. The administrator reviews the returned signature content and display name to ensure compliance with the company’s branding policy. If discrepancies are found, the IT team can follow up with the employee or use automation to standardize signatures across the domain.

This process is especially useful when onboarding new employees or during company-wide rebranding efforts.