# How to use the email verification action in Futuria CRM workflows

> Learn how to use the email verification action in Futuria CRM workflows to cut bounces, protect your sender reputation and improve deliverability.

Author: Futuria Support Team · Published: June 18, 2026 · Reading time: 7 min read

Source: https://futuriamarketing.com/en/supporto/azione-verifica-email-workflow/

---

## What is the email verification action in workflows?

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

The email verification action can be added at any point in a workflow, but it is most commonly placed before an email sending action. The system checks the contact's email address and returns a verification result that can be used to continue the workflow, divert the contact onto a different path, or prevent sending to addresses that could damage deliverability.

Email verification can check signals such as:

- Syntax correctness
- Domain validity
- Mailbox existence
- Risk indicators, such as disposable, inactive or low-quality email addresses

## Key benefits of the email verification action in workflows

- **Reduces email bounces:** validates email addresses before sending to reduce failed delivery attempts.
- **Protects your sender reputation:** avoids sending to invalid or risky addresses that could negatively affect your domain reputation.
- **Improves deliverability:** supports better inbox placement by sending to higher-quality email addresses.
- **Improves workflow decisions:** uses verification results to continue, branch or stop email-related actions.
- **Supports cleaner contact communication:** focuses email automation on contacts whose addresses are more likely to receive messages.

## Prerequisites for email verification

Email verification must be available and enabled for the account before the workflow action can be used. Confirming access before you build the workflow helps prevent configuration issues and ensures verification can run as expected.

Before using this action, make sure that:

- **Email verification is enabled for the account**.
- The **contact is not excluded from verification**. If the contact is excluded, the email verification action will be skipped.
- The workflow has access to the contact's email address.
- The action is placed before the email sending steps.
- Any conditional logic (If/Else) is configured after the email verification action.

## 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 the following actions. Placing this action before email sending steps gives the workflow the chance to assess email quality before dispatch.

When a contact reaches the email verification action, Futuria CRM evaluates the address and determines whether it appears valid, risky or invalid. The workflow can then use the verification result in subsequent actions or in conditional logic.

Common results include:

- **Valid:** the email address passed verification and is more likely to be safe to send to.
- **Risky:** the email address may be deliverable but shows risk signals that could affect deliverability or sender reputation.
- **Invalid:** the email address failed verification and should generally be excluded from sending.

The workflow outcome depends on how you configure the steps after verification. You can let verified contacts continue, route risky contacts to a review or an alternative path, or stop sending to 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 that 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 an email sending action
- Route risky email addresses to a separate branch
- Skip email sending for invalid addresses
- Stop the workflow or redirect contacts to another action

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

## Recommended placement in a workflow

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

**Recommended workflow order:**

1. The trigger starts the workflow.
2. Add the email verification action.
3. Add an If/Else action or a condition based on verification.
4. Send emails only to contacts that meet your verification criteria.
5. Route risky or invalid contacts to an alternative path, an internal notification, a tag or an exit from the workflow.

**Example workflow path:**

- The contact enters the workflow
- Email verification runs
- If the email is verified, proceed to sending the email
- If the email is risky or invalid, enable DND (Do Not Disturb) or move the contact to another path

![Example of a workflow path with the email verification action in Futuria CRM.](https://jumpshare.com/share/hPf0HP6SJCEs3RFTGBoQ+/Screen+Shot+2026-05-12+at+21.04.19.png)

## How to use the email verification action in workflows

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

> **Note:** make sure that **email verification** is **enabled** for the **account** and that the **contact is not excluded from verification**.

1. Go to **Automation** > **Workflows**.
2. **Open** an **existing** workflow or **create** a **new** one.

![Screenshot of the workflows section in Futuria CRM.](https://jumpshare.com/share/YRpMsB4TIg2S2w1O5fAU+/Screen+Shot+2026-05-12+at+21.18.02.png)

1. Add a relevant trigger such as **Contact Created**.

![Adding a 'Contact Created' trigger to a workflow.](https://jumpshare.com/share/JoSzc90A3vIvZVV6Ji3U+/Screen+Shot+2026-05-12+at+21.24.47.png)

1. Click **+** to **add** a **new action**.
2. Search for and select **Verify Email**, then click the **Save Action** button.

![Selecting the 'Verify Email' action inside a workflow.](https://jumpshare.com/share/q1IOQJjtSDyL81OkUavZ+/Screen+Shot+2026-05-12+at+21.26.18.png)

1. Place the action before any email sending action, such as **Send Email**.
2. Add an **If/Else condition** action after email verification if you want to branch contacts based on the verification results.
3. **Configure** the **logic** for valid, risky or invalid email addresses.
4. Route verified contacts towards the email sending steps.
5. Route risky or invalid contacts to an alternative path such as DND (Do Not Disturb), or stop the workflow.

![Configuring If/Else conditional logic based on the email verification result.](https://jumpshare.com/share/bvP1Glj1pzRVwuc5dCRv+/GIF+Recording+2026-05-12+at+21.33.23.gif)

1. Test the workflow to confirm that contacts follow the expected path.
2. **Save** and **Publish** the workflow.

!['Publish' button to activate the workflow in Futuria CRM.](https://jumpshare.com/share/C7qmddV32Yz4AK5VkISI+/Screen+Shot+2026-05-12+at+21.35.41.png)

## 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 sound email sending practices for better deliverability results.

- Place email verification before every important email step where address quality is critical.
- Use If/Else logic to separate verified contacts from risky or invalid ones.
- Avoid sending marketing or automated emails to invalid addresses.
- Treat risky results with caution, especially for high-volume campaigns.
- Use tags, notes or alternative paths to track contacts with risky or invalid emails.
- Review the workflow execution history while testing your verification logic.
- Use email verification as part of a wider deliverability strategy; it does not guarantee inbox placement.

## Frequently Asked Questions

##### Where should I place the email verification action in my workflow?

Place it before any email sending action or related step. This allows the workflow to validate the contact's email address before sending.

##### Does email verification automatically stop the workflow?

The outcome depends on how the workflow is configured after the action. You can let contacts continue, branch them using If/Else logic, or stop email-related steps for risky or invalid addresses.

##### What does a risky email mean?

A risky email may be deliverable but shows signals that could affect your bounce rate, sender reputation or deliverability. You may want to route risky contacts to a separate path instead of sending automatically.

##### Should I send emails to invalid addresses?

Invalid addresses should generally be excluded from sending to reduce bounces and protect your sender reputation.

##### Can I use email verification with If/Else conditions?

Yes. Add an If/Else action after email verification and use the available condition on the verification result, such as `isEmailVerified`, to control the contact's path.

##### 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 configuration, engagement and sound email sending practices.

##### 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.

##### Do I need email verification enabled before using this action?

Yes. Email verification must be enabled for the account before it can be used in workflows.