---
title: Connect mailfloss to Make
slug: connect-mailfloss-to-make
description: Connect mailfloss to Make with an API key, then verify new sign-ups in a scenario. Covers each mailfloss module and common errors.
createdAt: 2026-11-19T15:14:19.918Z
---

Use the mailfloss app in Make to add email verification to your scenarios. Check each new address the moment it arrives, verify a whole list as a batch, or start a scenario when mailfloss finds an undeliverable address or finishes a job.

## Before you start

You need a Make account and a mailfloss account with verification credits. Verifying one address uses one credit. A batch uses one credit per address. Make counts its own operations against your Make plan; those are separate from mailfloss credits.

## Create a mailfloss API key

1. In mailfloss, open **Developers**. The **API keys** tab opens.
2. Click **Create API key**. Give the key a name you'll recognize, such as "Make", and click **Create API key**.

   ::Image[]{src="https://api.archbee.com/api/optimize/yGUejq6E8IJ_sYX6JSjSr/XYvhFWVHTWWSL1Gh1q2uj_0-mailfloss-create-api-key.png" size="144" alt="The Create an API key form in mailfloss, with the name Make" isUploading="false" initialPath="0-mailfloss-create-api-key.png" githubPath="0-mailfloss-create-api-key.png" width="1440" height="757" darkWidth="1440" darkHeight="757" showCaption="false"}
3. Copy the key. mailfloss shows it only once.

A key with **Full access** works with every module. If you choose **Restricted**, a module that needs access you didn't grant fails with a 403 error.

## Connect mailfloss in Make

1. In a Make scenario, click **+** to add a module and search for **mailfloss**. Choose the mailfloss app marked **Verified**.

   ::Image[]{src="https://api.archbee.com/api/optimize/yGUejq6E8IJ_sYX6JSjSr/-BaY7nA-6IogBUP-Lb660_1-make-mailfloss-modules.png" size="64" alt="The mailfloss app in Make, marked Verified, with its modules" isUploading="false" initialPath="1-make-mailfloss-modules.png" githubPath="1-make-mailfloss-modules.png" width="640" height="560" showCaption="false"}
2. Choose a module, for example **Verify an email address**.
3. Under **Connection**, click **Create a connection**.
4. Paste your API key into **API key** and click **Save**. Make checks the key before it saves the connection.

   ::Image[]{src="https://api.archbee.com/api/optimize/yGUejq6E8IJ_sYX6JSjSr/zwKcPiA7N2WnqLXyMesfG_2-make-create-connection.png" size="47" alt="Make's Create a connection window for mailfloss" isUploading="false" initialPath="2-make-create-connection.png" githubPath="2-make-create-connection.png" width="474" height="480" showCaption="false"}

You only connect once. Other mailfloss modules can use the same connection.

## Starter scenario: verify new sign-ups before they reach your list

This scenario checks each new sign-up and passes on only the addresses that pass verification.

1. Add a trigger for new sign-ups. This example uses **Webhooks > Custom webhook**: click **Add**, name the webhook, and copy its URL into your form's settings so the form posts each sign-up there. Then click **Detect new values** and submit a test sign-up, so Make learns the form's fields. You can use your form app's own trigger instead.
2. Add **mailfloss > Verify an email address**. In **Email address**, map the email field from your trigger.

   ::Image[]{src="https://api.archbee.com/api/optimize/yGUejq6E8IJ_sYX6JSjSr/wfobzh8L3tjvcbFbEH5PS_3-make-verify-module.png" size="126" alt="The Verify an email address module, with the email mapped from the webhook" isUploading="false" initialPath="3-make-verify-module.png" githubPath="3-make-verify-module.png" width="1260" height="420" showCaption="false"}
3. Add the module that adds a contact to your list, such as your email platform's module for adding a subscriber. This example uses **Data store > Add/replace a record**, with a data store named "Verified sign-ups" that has the fields **Email** and **Status**. Leave **Key** empty so Make creates one, and map **Email** and **Status** from the mailfloss module.
4. Click the link between mailfloss and that module, then click **Set up a filter**. Name the filter. For the condition, choose mailfloss's **Status**, then **Text operators: Equal to**, and enter `passed`.

   ::Image[]{src="https://api.archbee.com/api/optimize/yGUejq6E8IJ_sYX6JSjSr/r5v0SufehPyAbZROUZtEa_4-make-filter-passed.png" size="48" alt="A filter that lets only addresses with the status passed through" isUploading="false" initialPath="4-make-filter-passed.png" githubPath="4-make-filter-passed.png" width="480" height="500" showCaption="false"}

   The finished scenario looks like this:

   ::Image[]{src="https://api.archbee.com/api/optimize/yGUejq6E8IJ_sYX6JSjSr/cQg3DNEp0_KeS6o3rYV_f_5-make-starter-scenario.png" size="118" alt="The starter scenario: webhook, mailfloss, the Address passed filter, then a data store" isUploading="false" initialPath="5-make-starter-scenario.png" githubPath="5-make-starter-scenario.png" width="1180" height="380" showCaption="false"}
5. Click **Run once** and send a test sign-up. When the run ends, click the bubble above the mailfloss module to see the result.

   ::Image[]{src="https://api.archbee.com/api/optimize/yGUejq6E8IJ_sYX6JSjSr/tgL30nioNz4yni-xZVqPe_6-make-verify-result.png" size="68" alt="The result for jane.doe@example.com: status undeliverable, reason illegit" isUploading="false" initialPath="6-make-verify-result.png" githubPath="6-make-verify-result.png" width="680" height="610" showCaption="false"}

   In this test, the address came back **undeliverable**, so the filter stops it before it reaches your list.
6. When the scenario works, switch it on so it runs for every new sign-up.

When mailfloss spots a likely typo, **Suggestion** holds a corrected address. Map it to ask the person to confirm their address.

Status is one of `passed`, `undeliverable`, `risky` or `unknown`. An `unknown` result isn't a confirmed pass.

## Modules

- **Watch verification events** (trigger): starts a scenario when mailfloss sends an event you choose, such as a finished batch job, an undeliverable or risky address, or a contact that mailfloss fixed or removed. Needs a mailfloss plan that includes webhooks.
- **Verify an email address**: verifies one address in real time and returns its status, the reason and a suggested fix for typos. Uses one credit.
- **Start a batch verification**: submits a list of addresses for verification and returns the job ID.
- **Get a batch verification**: returns a job's status and, once it finishes, a summary of its results.
- **List batch verification results**: returns one bundle per verified address.
- **Make an API call**: calls any mailfloss API endpoint with your connection. Enter a path such as `/v1/organization`; the connection adds your key.

## Troubleshooting

- **\[401] Invalid API key**: mailfloss rejected the key. It may be mistyped, revoked or expired. Create a new key under **Developers > API keys**. Then, in the module, click **Add** next to **Connection** and create a connection with the new key.
- **\[402] Insufficient credits**: your mailfloss account is out of verification credits. Add credits in mailfloss under **Payments & Plans**, then run the scenario again.
- **\[403]**: the key is valid but can't do this. A **Restricted** key can cause this; use a key with **Full access**, or one that includes the access the module needs.
- **Watch verification events doesn't work**: webhooks need a mailfloss plan that includes them: Business or Pro, or Lite with the Webhooks add-on.

## Links

- [mailfloss on Make](https://www.make.com/integrations/mailfloss)
- [mailfloss API reference](https://developers.mailfloss.com)
