Skip to content
Workflows

Workflow Action - Email Verification

Learn how to use the Email Verification Action in GHL Customer Care workflows to validate emails, reduce bounces, branch contacts, and improve deliverability.

6 min read1,453 words6 explained images
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
On this page
  1. Key Benefits of Email Verification Action in Workflows
  2. Prerequisites for Email Verification
  3. How Email Verification Works in Workflows
  4. Using Email Verification Results in Workflow Logic
  5. Recommended Placement in a Workflow
  6. How To Use the Email Verification Action in Workflows
  7. Best Practices for Email Verification in Workflows
  8. Frequently Asked Questions
  9. Related Articles

Email Verification in Workflows helps validate contact email addresses before email-related workflow steps run. By checking email quality before sending, you can reduce bounces, protect sender reputation, and improve the quality of automated outreach. This article explains what the Email Verification action does, how to configure it, and how to use verification results to control workflow logic in GHL Customer Care.

TABLE OF CONTENTS

What is Email Verification Action in Workflows?

The Email Verification action validates a contact’s email address inside a workflow before the contact reaches an email step. This helps confirm whether an email address is suitable for sending and gives you more control over how contacts move through automation based on email quality.

The Email Verification action can be added anywhere inside a workflow, but it is most commonly placed before a Send Email action. The system checks the contact’s email address and returns a verification outcome that can be used to continue the workflow, branch the contact into a different path, or prevent sending to addresses that may harm deliverability.

Email verification may check signals such as:

  • Syntax correctness

  • Domain validity

  • Mailbox existence

  • Risk indicators, such as disposable, inactive, or low-quality email addresses

Key Benefits of Email Verification Action in Workflows

  • Reduces email bounces: Validate email addresses before sending to reduce failed delivery attempts.

  • Protects sender reputation: Avoid sending to invalid or risky addresses that may negatively affect domain reputation.

  • Improves deliverability: Support better inbox placement by sending to higher-quality email addresses.

  • Improves workflow decisioning: Use verification results to continue, branch, or stop email-related actions.

  • Supports cleaner contact communication: Focus email automation on contacts with email addresses that are more likely to receive messages.

Prerequisites for Email Verification

Email Verification must be available and enabled for the sub-account before the workflow action can be used. Confirming access before building the workflow helps prevent setup issues and ensures verification can run as expected.

Before using this action, make sure:

  • Email Verification is enabled for the sub-account.

  • The Contact is Not Excluded from Verification

    If the contact is excluded from verification, the Email Verification action will be skipped.

  • The workflow has access to the contact’s email address.

  • The action is placed before email-sending steps.

  • Any If/Else or condition logic is configured after the Email Verification action.

For enablement and billing details, refer to How to Enable and Rebill LC Email Verification.

How Email Verification Works in Workflows

Email Verification runs as part of the workflow sequence and checks the contact’s email address before the contact proceeds to later actions. Placing this action before email steps gives the workflow a chance to evaluate email quality before sending.

When a contact reaches the Email Verification action, GHL Customer Care evaluates the email address and determines whether it appears valid, risky, or invalid. The workflow can then use the verification result in later actions or conditional logic.

Common outcomes include:

  • Valid: The email address passed verification and is more likely to be safe for sending.

  • Risky: The email address may be deliverable but has risk signals that could affect deliverability or sender reputation.

  • Invalid: The email address did not pass verification and should generally be excluded from email sends.

The workflow outcome depends on how you configure the steps after verification. You can allow verified contacts to continue, route risky contacts into a review or alternate path, or stop email sends for invalid addresses.

Using Email Verification Results in Workflow Logic

Verification results are most useful when paired with workflow conditions. Conditional logic lets you decide what happens after the email address is checked, so contacts do not all have to follow the same path.

You can use Email Verification results to:

  • Continue the workflow for verified email addresses

  • Send verified contacts to a Send Email action

  • Route risky email addresses to a separate branch

  • Skip email sending for invalid email addresses

  • Stop the workflow or redirect contacts to another action

A common setup is to add an If/Else action after Email Verification and use the email verification result as the condition. For example, contacts with isEmailVerified = true can continue to the Send Email action, while contacts that do not meet the condition can be routed to another branch.

The Email Verification action should usually be placed before any action that sends an email. This ensures the workflow checks email quality before attempting delivery.

Recommended workflow order:

  1. Trigger starts the workflow.

  2. Add the Email Verification action.

  3. Add an If/Else action or verification-based condition.

  4. Send emails only to contacts that meet your verification criteria.

  5. Route risky or invalid contacts to an alternate path, internal notification, tag, or workflow exit.

Example workflow path:

  • Contact enters workflow

  • Email Verification runs

  • If email is verified, continue to Send Email

  • If email is risky or invalid, enable DnD or move the contact to another path

Recommended Placement in a Workflow (image 1 of 6) What this shows Contact enters workflow Email Verification runs If email is verified, continue to Send Email If email is risky or invalid, enable DnD or… What this shows Illustrates the "Recommended Placement in a Workflow" section of "Workflow Action - Email Verification". This screenshot appears in the "Recommended Placement in a Workflow" section of "Workflow Action - Email Verification". The text alongside this image reads: Contact enters workflow Email Verification runs If email is verified, continue to Send Email If email is risky or invalid, enable DnD or move the contact to another path. This part of the guide covers 3 fields, listed below. Immediately after, the guide continues: Proper setup ensures the workflow checks email quality before sending messages. Adding the action before email steps and pairing it with decision logic gives you better control over which contacts receive automated emails. Image 1 of 6 What this coversContact enters workflow Email Verification runs If email is verified, continue to Send Email If email is risky or invalid, enable DnD or move the contact to another path
Fields in this part of the guide Contact enters workflowEmail Verification runsIf email is verified, continue to Send Email
Next stepProper setup ensures the workflow checks email quality before sending messages. Adding the action before email steps and pairing it with decision logic gives you better control over which contacts receive automated emails.
Example values
Email Verification runs
priya.raman@northgatedental.com
If email is verified, continue to Send Email
priya.raman@northgatedental.com

Illustrative values showing the expected format. They are not read from the screenshot.

All 5 steps in this procedure
  1. Trigger starts the workflow.
  2. Add the Email Verification action.
  3. Add an If/Else action or verification-based condition.
  4. Send emails only to contacts that meet your verification criteria.
  5. Route risky or invalid contacts to an alternate path, internal notification, tag, or workflow exit.

How To Use the Email Verification Action in Workflows

Proper setup ensures the workflow checks email quality before sending messages. Adding the action before email steps and pairing it with decision logic gives you better control over which contacts receive automated emails.

Note: Make sure Email Verification is enabled for the sub-account and the Contact is Not Excluded from Verification.

  1. Go to Automation > Workflows.

  2. Open an existing workflow or create a new workflow.

    Step 2 of 12: Open an existing workflow or create a new workflow What this shows Step 2 of 12: Open an existing workflow or create a new workflow. What this shows Shows where to go for step 2 of 12 in the "How To Use the Email Verification Action in Workflows" section of "Workflow Action - Email Verification". This screenshot accompanies step 2 of 12 in the "How To Use the Email Verification Action in Workflows" section of "Workflow Action - Email Verification". At this point in the walkthrough you open an existing workflow or create a new workflow. The navigation path used here is Automation > Workflows. The next step is to add a relevant trigger like Contact Created. Step 2 of 12Path: Automation > WorkflowsImage 2 of 6 Where to goOpen an existing workflow or create a new workflow.
    Buttons and menus referenced OpenexistingcreatenewworkflowEmail VerificationenabledsubaccountContactNot Excluded from Verification.Automation
    Next stepAdd a relevant trigger like Contact Created.
    All 12 steps in this procedure
    1. Go to Automation > Workflows.
    2. Open an existing workflow or create a new workflow. this image
    3. Add a relevant trigger like Contact Created.
    4. Click + to add a New Action.
    5. Search for and select Email Verification and click on Save Action button.
    6. Place the action before any email action, such as Send Email.
    7. Add an If/Else C ondition action after Email Verification if you want to branch contacts based on verification results.
    8. Configure the logic for valid, risky, or invalid email addresses.
    9. Route verified contacts toward email steps.
    10. Route risky or invalid contacts to an alternate path like DnD, or stop the workflow.
    11. Test the workflow to confirm contacts follow the expected path.
    12. Save and Publish the workflow.

  3. Add a relevant trigger like Contact Created.

    Step 3 of 12: Add a relevant trigger like Contact Created What this shows Step 3 of 12: Add a relevant trigger like Contact Created. What this shows Shows what this covers for step 3 of 12 in the "How To Use the Email Verification Action in Workflows" section of "Workflow Action - Email Verification". This screenshot accompanies step 3 of 12 in the "How To Use the Email Verification Action in Workflows" section of "Workflow Action - Email Verification". At this point in the walkthrough you add a relevant trigger like Contact Created. The navigation path used here is Automation > Workflows. The next step is to click + to add a New Action. Step 3 of 12Path: Automation > WorkflowsImage 3 of 6 What this coversAdd a relevant trigger like Contact Created.
    Buttons and menus referenced Contact CreatedEmail VerificationenabledsubaccountContactNot Excluded from Verification.AutomationWorkflowsOpenexistingcreate
    Next stepClick + to add a New Action.
    All 12 steps in this procedure
    1. Go to Automation > Workflows.
    2. Open an existing workflow or create a new workflow.
    3. Add a relevant trigger like Contact Created. this image
    4. Click + to add a New Action.
    5. Search for and select Email Verification and click on Save Action button.
    6. Place the action before any email action, such as Send Email.
    7. Add an If/Else C ondition action after Email Verification if you want to branch contacts based on verification results.
    8. Configure the logic for valid, risky, or invalid email addresses.
    9. Route verified contacts toward email steps.
    10. Route risky or invalid contacts to an alternate path like DnD, or stop the workflow.
    11. Test the workflow to confirm contacts follow the expected path.
    12. Save and Publish the workflow.

  4. Click + to adda New Action.

  5. Search for and select Email Verification and click on Save Action button.

    Step 5 of 12: Search for and select Email Verification and click on Save Action button What this shows Step 5 of 12: Search for and select Email Verification and click on Save Action button. What this shows Shows what to choose for step 5 of 12 in the "How To Use the Email Verification Action in Workflows" section of "Workflow Action - Email Verification". This screenshot accompanies step 5 of 12 in the "How To Use the Email Verification Action in Workflows" section of "Workflow Action - Email Verification". At this point in the walkthrough you search for and select Email Verification and click on Save Action button. The navigation path used here is Automation > Workflows. The next step is to place the action before any email action, such as Send Email. Step 5 of 12Path: Automation > WorkflowsImage 4 of 6 What to chooseSearch for and select Email Verification and click on Save Action button.
    Buttons and menus referenced Email VerificationSave ActionenabledsubaccountContactNot Excluded from Verification.AutomationWorkflowsOpenexistingcreate
    Next stepPlace the action before any email action, such as Send Email.
    All 12 steps in this procedure
    1. Go to Automation > Workflows.
    2. Open an existing workflow or create a new workflow.
    3. Add a relevant trigger like Contact Created.
    4. Click + to add a New Action.
    5. Search for and select Email Verification and click on Save Action button. this image
    6. Place the action before any email action, such as Send Email.
    7. Add an If/Else C ondition action after Email Verification if you want to branch contacts based on verification results.
    8. Configure the logic for valid, risky, or invalid email addresses.
    9. Route verified contacts toward email steps.
    10. Route risky or invalid contacts to an alternate path like DnD, or stop the workflow.
    11. Test the workflow to confirm contacts follow the expected path.
    12. Save and Publish the workflow.

  6. Place the action before any email action, such as Send Email.

  7. Add an If/Else Condition action after Email Verification if you want to branch contacts based on verification results.

  8. Configure the logic for valid, risky, or invalid email addresses.

  9. Route verified contacts toward email steps.

  10. Route risky or invalid contacts to an alternate path like DnD, or stop the workflow.

    Step 10 of 12: Route risky or invalid contacts to an alternate path like DnD, or stop… What this shows Step 10 of 12: Route risky or invalid contacts to an alternate path like DnD, or stop the workflow. What this shows Shows what this covers for step 10 of 12 in the "How To Use the Email Verification Action in Workflows" section of "Workflow Action - Email Verification". This animation accompanies step 10 of 12 in the "How To Use the Email Verification Action in Workflows" section of "Workflow Action - Email Verification". At this point in the walkthrough you route risky or invalid contacts to an alternate path like DnD, or stop the workflow. The navigation path used here is Automation > Workflows. The next step is to test the workflow to confirm contacts follow the expected path. Step 10 of 12Path: Automation > WorkflowsImage 5 of 6 What this coversRoute risky or invalid contacts to an alternate path like DnD, or stop the workflow.
    Buttons and menus referenced Email VerificationenabledsubaccountContactNot Excluded from Verification.AutomationWorkflowsOpenexistingcreatenew
    Next stepTest the workflow to confirm contacts follow the expected path.
    All 12 steps in this procedure
    1. Go to Automation > Workflows.
    2. Open an existing workflow or create a new workflow.
    3. Add a relevant trigger like Contact Created.
    4. Click + to add a New Action.
    5. Search for and select Email Verification and click on Save Action button.
    6. Place the action before any email action, such as Send Email.
    7. Add an If/Else C ondition action after Email Verification if you want to branch contacts based on verification results.
    8. Configure the logic for valid, risky, or invalid email addresses.
    9. Route verified contacts toward email steps.
    10. Route risky or invalid contacts to an alternate path like DnD, or stop the workflow. this image
    11. Test the workflow to confirm contacts follow the expected path.
    12. Save and Publish the workflow.

  11. Test the workflow to confirm contacts follow the expected path.

  12. Save and Publish the workflow.

    Step 12 of 12: Save and Publish the workflow What this shows Step 12 of 12: Save and Publish the workflow. What this shows Shows how to confirm for step 12 of 12 in the "How To Use the Email Verification Action in Workflows" section of "Workflow Action - Email Verification". This screenshot accompanies step 12 of 12 in the "How To Use the Email Verification Action in Workflows" section of "Workflow Action - Email Verification". At this point in the walkthrough you save and Publish the workflow. For context, this section explains: Proper setup ensures the workflow checks email quality before sending messages. Adding the action before email steps and pairing it with decision logic gives you better control over which contacts receive automated emails. The navigation path used here is Automation > Workflows. Step 12 of 12Path: Automation > WorkflowsImage 6 of 6 How to confirmSave and Publish the workflow.
    Buttons and menus referenced SavePublishEmail VerificationenabledsubaccountContactNot Excluded from Verification.AutomationWorkflowsOpenexisting
    All 12 steps in this procedure
    1. Go to Automation > Workflows.
    2. Open an existing workflow or create a new workflow.
    3. Add a relevant trigger like Contact Created.
    4. Click + to add a New Action.
    5. Search for and select Email Verification and click on Save Action button.
    6. Place the action before any email action, such as Send Email.
    7. Add an If/Else C ondition action after Email Verification if you want to branch contacts based on verification results.
    8. Configure the logic for valid, risky, or invalid email addresses.
    9. Route verified contacts toward email steps.
    10. Route risky or invalid contacts to an alternate path like DnD, or stop the workflow.
    11. Test the workflow to confirm contacts follow the expected path.
    12. Save and Publish the workflow. this image

Best Practices for Email Verification in Workflows

Using Email Verification with clear workflow logic helps reduce unnecessary sends and keeps automated communication focused on contacts with better-quality email addresses. Combine verification with strong email-sending practices for better deliverability outcomes.

  • Place Email Verification before every important email step where email quality matters.

  • Use If/Else logic to separate verified contacts from risky or invalid contacts.

  • Avoid sending marketing or automated emails to invalid addresses.

  • Treat risky results carefully, especially for high-volume campaigns.

  • Use tags, notes, or alternate paths to track contacts with risky or invalid emails.

  • Review workflow execution history when testing verification logic.

  • Use Email Verification as part of a broader deliverability strategy; it does not guarantee inbox placement.

Frequently Asked Questions

Q: Where should I place the Email Verification action in my workflow?
Place it before any Send Email action or email-related step. This lets the workflow validate the contact’s email address before sending.

Q: Does Email Verification automatically stop the workflow?
The outcome depends on how the workflow is configured after the action. You can allow contacts to continue, branch them using If/Else logic, or stop email-related steps for risky or invalid emails.

Q: What does a risky email mean?
A risky email may be deliverable but has signals that could affect bounce rate, sender reputation, or deliverability. You may want to route risky contacts to a separate path instead of sending automatically.

Q: Should I send emails to invalid addresses?
Invalid addresses should generally be excluded from email sends to reduce bounces and protect sender reputation.

Q: Can I use Email Verification with If/Else conditions?
Yes. Add an If/Else action after Email Verification and use the available verification result condition, such as isEmailVerified, to control the contact’s path.

Q: Does Email Verification guarantee inbox placement?
No. Email Verification helps reduce sending to poor-quality addresses, but inbox placement also depends on sender reputation, content quality, domain setup, engagement, and email best practices.

Q: Does the Email Verification action validate emails in real time?
Yes. The action checks the contact’s email address when the contact reaches that step in the workflow.

Q: Do I need Email Verification enabled before using this action?
Yes. Email Verification must be enabled for the sub-account before it can be used in workflows.

Was this guide helpful?

Related guides

Workflow Action - Goal Event6 min read · 11 imagesWorkflow Action - Dare/Time Formatter2 min read · 3 imagesWorkflow Action - Number Formatter2 min read · 5 imagesConversation AI Post-Appointment Booking Actions1 min read · 4 images