Email verification in your Make scenarios
Add the verified mailfloss app to a Make scenario to check each new address before it reaches your list. Verify one address in real time, verify a list as a batch, or start a scenario when mailfloss sends an event.
What the mailfloss app does in Make
Every result has a status of passed, undeliverable, risky or unknown. Make an API call reaches any other mailfloss API endpoint.
Connect, map, then filter
The setup guide has every step, with screenshots.
When should I use the Make app instead of a native integration?
If your list lives in an email platform mailfloss connects to directly, use that integration: mailfloss checks the list for you, with no scenario to maintain.
Use the Make app when the address comes from somewhere a native integration doesn’t reach, such as a custom form, a spreadsheet or a CRM step, or when you want the result to drive your own routing. To build verification into your own code, use the mailfloss email verification API; the Make app calls the same API.
