A set of HubSpot fixes makes syncing more reliable:
List imports read each list through HubSpot’s current Lists API.
Unsubscribes no longer fail in bursts. mailfloss now refreshes its HubSpot sign-in before it expires, so long cleanup runs no longer hit a wave of rejected requests.
Current HubSpot APIs: the remaining calls moved to HubSpot’s 2026-03 APIs. Nothing changes for you.
When you disconnect a HubSpot connection that signed in with HubSpot, mailfloss now also removes its app from your HubSpot portal, unless another mailfloss connection still uses that portal. Connections that use a private app key are not affected.
Reconnect and Finish connecting now repair the connection you selected, on every platform mailfloss supports. Before, some platforms showed “Account-specific reconnect is not available for this provider yet”, and you had to add the connection again. Now the connection keeps its settings and history, and its lists refresh once you’re back in.
API-key platforms: mailfloss checks the new key before saving it. If the platform refuses the key, your existing connection keeps working.
Sign-in platforms such as AWeber, Campaign Monitor, Drip, HubSpot and Intercom: choose Continue to the platform, approve access, and you return to the same connection.
If you cancel the sign-in screen, mailfloss now says that access was denied and how to try again.
During a trial, Payments & Plans now labels your balance as trial credits and explains when your full monthly credits start. For example: “Your trial includes up to 10,000 credits. Your full 25,000 monthly credits start when your trial ends.” The sidebar counter reads Trial credits too.
We also fixed the sidebar credit counters for people who belong to more than one organization. They now always show the same balance as Payments & Plans.
You can now connect Klaviyo in one click. Choose Connect with Klaviyo, approve access in Klaviyo, and you’re done. You don’t need to create or paste a private API key. The option sits above the private-key form in the integrations window and in onboarding.
Already connected with a private API key? Nothing changes, and it keeps working. To switch, open the connection’s Advanced tab and choose Switch to one-click connection.
Delete is now available for Klaviyo in Manual Mode and Auto Mode. In Klaviyo, Delete removes the profile and its history from your whole Klaviyo account, not just one list. If you connect with a private key that lacks the Data Privacy (write) scope, mailfloss unsubscribes the contact instead and tells you how to fix it. When you disconnect a one-click connection, mailfloss also removes its app from your Klaviyo account.
Each connection’s page in Integrations now shows a running import or verification, and what’s left to set up.
See a run’s progress, and stop it. While an import or verification run is in progress, a card above the tabs shows how far it has got. Stop run stops it after you confirm. Cleanup, Typo Fixer and Aggressiveness can’t be changed until the run ends.
Finish setup from Overview. A checklist starts with connecting your platform, then lists the setup steps that platform supports, such as choosing what happens to invalid emails and fixing typos. Each step is ticked off as you finish it. A step your plan doesn’t include shows Upgrade required and the plan or add-on that unlocks it. You can hide the checklist for each connection.
See Instafloss working. When Instafloss is on for a connection, Overview shows whether it’s Live, Listening, Quiet or Paused. Open the live view to see up to five recent subscribers and what happened to each. Addresses stay hidden until you click Show addresses.
Interrupted imports pick up where they stopped. GoHighLevel, Mailchimp and Ghost imports now resume from where they left off instead of starting over. Ghost and Iterable imports that run out of retries now stop cleanly instead of hanging as pending.
Reconnecting keeps your settings. Reconnect and Finish connecting on a Gist, Keap or GoHighLevel connection now act on the account you selected. If authorization fails, your existing connection, settings and history stay as they were.
HubSpot real-time checks retry after a failure. If we couldn’t fetch a new HubSpot contact, we now retry instead of skipping that contact for an hour.
Old API jobs no longer block new ones. The limit on pending bulk verification jobs no longer counts jobs older than 24 hours, so a stuck old job can’t block your new submissions.
HubSpot connections have moved off the OAuth endpoints HubSpot is retiring in February 2027. Nothing changes for you.
Typo Fixer and duplicate contacts. When Typo Fixer corrects an address that already belongs to another contact in ActiveCampaign, ActiveCampaign rejects the change. mailfloss didn’t recognize that rejection, so the fix kept retrying and never resolved. Now mailfloss runs your fallback action (update fields, unsubscribe or remove) straight away. Contacts you’ve set to review stay in your review queue.
Unsubscribes and field updates that partly fail. If an unsubscribe succeeded on one list but failed on another, or a field update failed partway, the failed part could be dropped. Now any failure is queued for a retry. An unsubscribe counts as done only when every list succeeded, and a field update only when every field did.
If an API key has an expiry date, mailfloss now emails your organization’s owner as it gets close: about 14 days, 3 days and 1 day before it expires. Each email gives the expiry date and links to the key manager in Account Settings, so you can replace the key before your integration stops working.
Keys that never expire, and keys you have already revoked, don’t trigger reminders. The email never includes the key itself.
After each write, Spotless reads the contact back from your email platform. If a write changed a field Spotless didn’t intend to touch, Spotless pauses writing to that connection.
The Spotless panel now tells you when that happens: the date writing was paused and why. Nothing else is written to that connection until you’ve reviewed it. When you’re ready, tick the confirmation and click Resume writing.
Spotless can now write phone number fixes back to Keap, alongside the name fixes it already writes. It updates only the phone slot it scanned and then checks every phone slot on the contact to confirm nothing else changed.
Name fixes are also more careful:
Initials with no vowels, like “CJ” and “TJ”, stay in capitals instead of becoming “Cj” and “Tj”. Roman numerals like “III” stay “III”.
Names with a stray run of capitals, like “marTIN”, are now fixed to “Martin”.
Short capitals that could be initials or an abbreviation, like “DR” or “MC”, are left alone rather than guessed at.
New Constant Contact connections now use Constant Contact’s v3 API. To connect, you create a private app in your own Constant Contact developer portal and paste its Client ID and Client Secret into mailfloss. The connect form walks you through each step.
Existing Constant Contact connections keep working as they are, and their page has a link to re-authorize the legacy connection.
On the new connection:
Unsubscribes are sent the way the v3 API expects, so a contact you unsubscribe stays unsubscribed in Constant Contact.
Spotless scans your Constant Contact contacts and can write first name, last name and phone fixes back. It reads the whole contact first, checks it again right before writing, and skips the update if anything changed. Writeback stays off until you turn it on.
We also fixed an error that stopped Constant Contact imports started from the dashboard.
Spotless can now write its fixes straight back to your ActiveCampaign contacts, so you don’t have to copy them over by hand.
When you apply fixes, Spotless sends only first name, last name and phone number fixes to ActiveCampaign. It doesn’t write custom fields, list memberships or any other contact field.
After each write, Spotless reads the contact back. If anything it didn’t write has changed, it stops writing to that connection and lets you know.
mailfloss now comes in dark. Open the theme picker in the navbar and choose Light, Dark or System. System follows whatever your device is set to, so the app switches with your computer.
It covers the whole app: every page, every panel, even checkout and the card form.
It’s brand new, so if something looks off, or you just love it, tell us.
Spotless can now write its fixes straight back to your GoHighLevel contacts, so you don’t have to copy them over by hand.
When you apply fixes, Spotless sends only first name, last name and phone number fixes to GoHighLevel. It doesn’t write custom fields, tags or any other contact field.
Spotless only writes to GoHighLevel after you turn on writeback for the connection. Until then, it keeps scanning and reporting as before.
The Integrations page has been rebuilt around the questions you actually ask: what’s connected, what needs my attention, and what is mailfloss doing to each list.
See what needs attention first. Connections that need reconnecting, aren’t finished connecting, or have addresses waiting for your decision are pulled to the top. Every connection shows its status in plain words: Active, Paused, Reconnect required or Not connected.
Multiple accounts on the same platform, done properly. When you’ve connected more than one account on the same email platform, they’re grouped into a single row that expands to show each account. You can rename connections, and “Connect another account” takes you straight to that platform. Once you have more than five connections, search and status filters help you find the one you need.
Everything for a connection in one place. Open a connection to find its settings in tabs:
Overview, with a Verify now button
Waiting for you, when addresses need your decision
Cleanup, where you choose what happens to bad addresses
Typo Fixer fixes misspelled addresses at popular email services: gmail.con becomes gmail.com.
Aggressiveness sets how strict the cleaning is. Normal removes what’s definitely undeliverable and leaves accept-all domains alone. Strict catches more, for rescuing a list with a bounce problem.
Schedule sets when mailfloss checks: Autofloss and Instafloss for new subscribers, Decay Protection to re-check the ones you already have.
Spotless finds and fixes bad names and phone numbers in your contacts.
We rebuilt how you get started with mailfloss. Setup now begins with what you want to do and takes you straight there, instead of dropping you on a blank dashboard.
Pick how you want to verify. A short walkthrough asks how your email addresses reach you, then takes you to the right setup:
Connect your email platform to clean an existing list, keep it clean automatically, or both
Upload a file or paste addresses for a one-off cleanup
Use the API to verify addresses in your own app
Add the JavaScript widget to catch bad addresses on your signup forms
Google Sheets or Airtable to verify addresses in place
Your choices carry through signup. What you picked before creating your account, including your plan and whether you want a one-time cleanup or ongoing cleaning, is still selected when you reach checkout and setup. You don’t have to choose twice.
Each path ends in a clear next step. When you connect an email platform, the last screen shows what happens next. For a one-time cleanup, that’s your cleanup request and whether it’s pending, sent or processing. For ongoing cleaning, it’s how your automation is set up.
Fewer interruptions. Reminders like confirming your email address or adding a passkey now wait until you’ve finished setup.
The in-app support widget now has a screenshot attach control. Add an image to your message and it comes through with your conversation, so we can see what you see.
Two integrations were still using API versions their vendors are retiring. We have moved them ahead of the deadlines:
Keap: unsubscribe, remove and the daily import now use Keap’s REST API instead of XML-RPC, which Keap is shutting down at the end of 2026.
ActiveCampaign: unsubscribes, contact lookups and list sync now use API v3, matching the rest of the integration.
Nothing changes in your settings. Existing connections keep working, and removals that quietly failed before now report an authorization problem so you can reconnect.
Separately, we fixed a Klaviyo lookup: an email address containing a ”+” was being read as if it contained a space, so the contact could not be found.
MailerLite accounts connected through the new MailerLite API now get the same removal options as our other integrations: Auto-Delete for automatic cleaning, and Delete as a Manual Mode action.
Under the hood, removals on new-API accounts now use MailerLite’s current subscriber delete endpoint, so a delete you request is the delete MailerLite performs.
GET /v1/account/timeline returns a feed of recent activity on your account, scoped to the caller.
Activity records now also say what started a job and what changed in your settings, so the timeline shows whether something was triggered by you, by a scheduled floss, or by an integration.
Addresses hosted on Google Workspace — a company using Google for its email rather than an @gmail.com address — are now labelled as such in email verification results.
If you use the API, /v1/verify returns provider: "gsuite" for these addresses instead of leaving them unlabelled, so you can tell business Google mailboxes apart from consumer Gmail.
mailfloss has always removed bad email addresses. Spotless now cleans other fields on the same contacts: names typed in ALL CAPS or all lowercase, phone numbers in inconsistent formats, and junk entries like “asdf asdf”.
Spotless scans and reports on 28 integrations. At launch it writes corrections back to 16 of them, and we’re adding more.
Nothing is ever written without your approval. Turn Spotless on per connection, run a scan, then review each proposed change and approve the ones you want. After every write, mailfloss reads the contact back from your provider to confirm the change actually landed — and stops if it didn’t. Clearing junk values is a separate opt-in, off by default, because that one can’t be undone.
Some mail servers use “greylisting” — they temporarily reject the first connection and expect a retry later. mailfloss now honors each server’s requested retry window per domain, instead of retrying on a fixed schedule.
The result: fewer addresses stuck as “unknown” and more accurate email verification for domains behind greylisting providers, with no change needed on your side.
Until now, Typo Fixer only corrected misspelled email providers — the gmail, hotmail and yahoo family. Mistyped company domains were left alone, so a subscriber who misspelled your own domain, or their employer’s, simply bounced.
Typo Fixer now spots those too, on every integration you can connect.
Company domains are treated differently on purpose. A provider misspelling has one obvious correction; a company misspelling often does not, and a confident wrong guess would hand you a real address belonging to someone else. So these are never applied for you. Each one is queued for you to approve or dismiss, and the queue tells you what we were actually able to confirm about the corrected address before you decide — whether the domain accepts mail, whether that specific mailbox could be verified, or whether the check was inconclusive.
The panel is also clearer about what happens without you: corrections that apply automatically are labelled as such, and the ones waiting on your decision say so.
You will find company-domain suggestions in the Typo Fixer panel alongside your existing ones.
Typo Fixer now catches a wider range of mistyped email providers. Our original rules only recognised misspellings close to a familiar shape, so addresses with a zero in place of an “o”, a doubled dot, or a stray character on the end were left alone and bounced.
Where those rules stay silent, a second pass now looks for the domain the person almost certainly meant — so more of your real subscribers get through instead of bouncing.
It is careful about what it will not touch: a suggested correction is dropped unless the corrected domain can actually receive mail.
Point mailfloss at a Klaviyo segment and it now behaves exactly like a list. Decay Protection runs on segments on both the weekly and monthly cadences, and autofloss picks them up automatically.
Choosing one is cleaner too — each segment appears once in the audience picker, and starting a scan on a segment scans that segment.
If you organise your Klaviyo audience with segments rather than lists, everything mailfloss does for a list is now available to you.
We’ve upgraded how mailfloss stores API keys. Keys are now kept as secure hashes rather than plaintext, and they no longer appear in our internal logs.
As part of this change, API keys are shown only once, at the moment you create them — they can no longer be viewed again from the dashboard. If you lose a key, just generate a new one from Settings → API keys.
If you use the mailfloss API, nothing changes about how you authenticate — your existing keys keep working.
Each SDK covers the full API surface: verify a single address, run batch verifications, manage ESP integrations and keyword rules, and read usage reports. They’re lightweight by design — the Python and Ruby clients have zero runtime dependencies.
Get an API key from your dashboard and see the developer docs to get started.
When the new mailfloss website launched, we said the same care was coming to the dashboard you use every day. Here it is.
mailfloss has been redesigned from top to bottom. Every screen — your dashboard, uploads, verification results, integrations, settings, sign-up and sign-in — has been rebuilt on a new design system.
What that means day to day: a cleaner, more consistent interface, clearer status colours across verification results, better contrast and readability, sharper charts, and layouts that hold up properly on smaller screens.
Everything is exactly where you left it. This is a new coat of paint, not a reorganisation — same pages, same workflow, same features, no need to relearn anything.
Addresses on Google Workspace domains that previously came back as accept_all are now more often resolved to a definitive result.
Google-hosted domains frequently accept mail for any address at the SMTP layer, which historically left us unable to tell a real mailbox from a fake one. Our Google-specific checks now confirm a mailbox’s existence from positive evidence rather than discarding it, so more of these addresses land as verified instead of unknown.
You can now sign in to mailfloss with a passkey — Touch ID, Face ID, Windows Hello, or a hardware security key like a YubiKey. No password to type, and nothing to remember. Passkeys are now the recommended way to sign in to mailfloss — they’re the most secure option we offer.
Passkeys are phishing-resistant: the credential is bound to mailfloss.com and never leaves your device, so it can’t be stolen from us or handed over on a lookalike site. Because signing in with a passkey already proves it’s you and that you hold the device, you won’t be asked for a two-factor code as well — it satisfies two-factor on its own.
Set one up under Settings → Account. This is entirely optional and additive: your password and existing two-factor setup keep working exactly as before, and you can add or remove passkeys at any time.
If you upload a list with more addresses than you have credits for, mailfloss now tells you exactly that — how many credits the list needs and how many you have — instead of the upload quietly failing.
Uploads are also now capped at your current balance, so a large list can’t start verifying and then stall part-way through once credits run out.
When you upload a list and mailfloss removes duplicate addresses, your import total and remaining-to-verify count now reflect what’s actually in the list.
Previously those numbers were calculated before de-duplication, so a list with a lot of repeats would show a higher total than the number of addresses really being verified — and the remaining count could drift as the job progressed. Both now come straight from your list, so what you see matches what you’re charged for.
Been invited to join a team on mailfloss but already have your own account? You can now accept that invitation directly — no second account, no new password, no support ticket.
Previously an invitation could only be accepted by someone signing up for the first time, which left existing users stuck at the invite link. Now you sign in as yourself, accept the seat, and switch into the organization straight away.
Who’s affected: anyone generating new mailfloss API keys.
New API keys are now issued exclusively in the secure mf_live_ format, stored hashed at rest — the old plaintext key format can no longer be generated. Existing legacy keys keep working, so nothing breaks today.
What to do: when convenient, create a new key from your dashboard’s API settings and swap it into your integration. We’ll give plenty of notice before legacy keys are retired entirely.
Connecting ClickFunnels to mailfloss is now a guided two-step flow: enter your API key, then pick exactly which team and workspace you want mailfloss to clean. No more guessing which workspace a key belongs to — you see your options and choose.
If you connected ClickFunnels before and had trouble, try reconnecting — the new flow sorts it out.
We audited every one of our email service provider integrations end to end and shipped fixes across more than 40 of them — HubSpot, Klaviyo, Mailchimp, ActiveCampaign, ConvertKit, Constant Contact, AWeber, Brevo, Beehiiv, and many more.
What you’ll notice: imports that previously could stall partway now run to completion, large lists page through reliably, typo fixes apply more accurately, and connection problems surface clearly instead of failing silently. If an integration ever felt flaky, it should feel noticeably more solid now.
You can now create, list, update, and delete webhook subscriptions directly through the mailfloss API — no dashboard visit needed. Point a subscription at your endpoint, choose the events you care about, and mailfloss notifies your systems the moment verifications finish.
Each subscription comes with a signing secret so you can verify that events really came from us. See the developer docs to get started.
The mailfloss website got a complete redesign — a cleaner look, a new brand, and pages that finally do a good job of explaining what mailfloss actually does for your list. Whether you are here to see how automatic email cleaning works, compare plans, or read up on a specific integration, everything is easier to find and quicker to read.
This is the first step of a bigger refresh. The same care is now coming to the dashboard you use every day, so the app you log into feels as sharp as the new site. More on that soon.
Nothing about your account, your connected platforms, or your cleaning schedule changes — same mailfloss, just a much nicer front door.
The mailfloss v1 API is now our recommended way to build on mailfloss. It uses modern Authorization: Bearer authentication, predictable resource-based endpoints, and clearer errors, pagination, and rate-limit headers — all covered by the interactive reference at developers.mailfloss.com.
Already building on the legacy API? Nothing breaks today — it stays fully supported until it sunsets on June 1, 2027, and moving over is usually a small change (swap a ?api_key= query parameter for an Authorization: Bearer header). Each legacy docs page links straight to its v1 replacement.
Your dashboard’s results table now keeps verified email addresses hidden by default — you see the verdicts (passed, reason, status) without contact data on screen. Click “View email addresses” whenever you want to show them. A more private dashboard, by default.
The full docs for the mailfloss v1 API are now live at developers.mailfloss.com. The centerpiece is an interactive reference: browse every v1 endpoint, see the exact request and response for each one, and try real calls right from the page. Because it is generated straight from the API, it stays in sync with the endpoints, so you build against what they actually do and catch problems before you ship.
There are also short guides for the parts people get stuck on: getting started, authentication, errors, pagination, rate limits, and connecting your email platform.
Already building on the legacy API? Nothing changes for you right now. It is still fully documented, now clearly marked as legacy, and it sunsets on June 1, 2027. Moving to v1 is a small change in most cases (swapping an ?api_key= query parameter for an Authorization: Bearer header), each legacy page links straight to its v1 replacement, and the quickstart is the best place to start.
You can now upload Excel spreadsheets in the file uploader, in the same place you upload CSV files. Supported formats are .xlsx, .xls, .xlsb, .xlsm, and .ods. Your spreadsheet is converted and processed just like a CSV upload, and your original file stays available for download.
A couple of things to know: we read the first worksheet of a multi-sheet workbook, and your file should have a header row, the same as a CSV.
There’s a bonus, too: the free Append results option now works for Excel uploads, not just CSVs. Switch it on before you export and we’ll add your email verification results — a status and reason for each address — back into your original spreadsheet.
Because Excel upload is now built in, we’ve removed the old standalone “Upload a spreadsheet” tool. We’ve also retired the “Import address book” option. If you previously imported contacts from an address book, you can export them to a spreadsheet or CSV and upload the file, or paste your addresses directly.
If your team uses our legacy API endpoints, here’s an important heads-up: we’re retiring them, and you’ll need to move to our current API before they’re switched off.
Deadline: June 1, 2027. After that date, the legacy endpoints will stop responding.
Does this affect you? Only if you call the legacy API directly from your own code or scripts. If you use our native integrations (Mailchimp, Klaviyo, HubSpot, GoHighLevel, and the rest) or Zapier, you’re all set — nothing changes for you.
What’s next: we’re putting the finishing touches on our current API and a full migration guide. We’ll post it right here in the changelog — and email it to you — as soon as it’s ready, well ahead of the deadline.
There’s plenty of runway, and we’re here to help. If you call the legacy API directly and want to get ahead of the migration, reach out to support any time.
We also sent this to your inbox earlier this week — this post is here so it’s easy to find and link back to.
If you’re connected to multiple integrations, you know the pain: a few report emails land in your inbox, and you have to open each one to figure out which integration it’s for.
Not anymore. Report emails now include the integration name right in the subject line.
So instead of:
“Your emails are flossed”
You’ll see:
“Your emails are flossed for Klaviyo (Main Store)”
Quick to scan, easy to sort, no more guessing.
This is especially useful if you’re managing multiple accounts or running different lists across different ESPs.
No action needed on your end. This is already live for all accounts. 🚀
GoHighLevel is an all-in-one marketing platform trusted by agencies and marketers to build funnels, automate workflows, and scale client results. And now, with mailfloss baked right into your GoHighLevel setup, keeping your email lists clean and performing at their best is easier than ever.
With the mailfloss + GoHighLevel integration, you get:
✅ Instant email verification the moment contacts are added
🛠 Real-time typo correction so you don’t lose leads to simple mistakes
🔄 Automated list cleaning—unsubscribe, delete, or update custom fields of bad emails
📬 Lower bounce rates and stronger inbox placement
💡 Improved sender reputation and campaign ROI with zero manual effort
Want to start sending smarter?
Just head to Integrations in your mailfloss dashboard and hit Add Integration to link your GoHighLevel account.
Less list anxiety, more results—this one’s for every agency and marketer who’s tired of wrestling with bad data. Go get it!
Say goodbye to email bounces—right from Airtable. With the new mailfloss Email Verifier extension, you can now clean your email lists without ever leaving your base.
✅ Verify emails directly in Airtable
⚡ Instantly check thousands of records
🔍 Identify invalid, risky, and typo-ridden addresses in seconds
Ready to protect your sender reputation and boost deliverability?
Encharge is a powerful marketing automation platform built to help you convert more leads, nurture customer relationships, and drive revenue—without the manual grind. And now, with mailfloss seamlessly integrated into your Encharge workflow, you can keep your email lists clean and conversion-ready—automatically.
With the mailfloss + Encharge integration, you’ll unlock:
✅ Real-time email verification at the point of capture
✍️ Automatic typo correction to save missed leads
🔁 Ongoing list cleaning and hygiene to protect sender reputation
📉 Reduced bounce rates and improved inbox placement
🚀 More efficient automations and higher email ROI
Ready to clean up your list and power up your automations? Head to Integrations in your mailfloss dashboard and click Add Integration to connect your Encharge account today.
We can’t wait to see how this new integration helps you maximize your campaign performance and simplify your workflow.
Tired of bouncing emails messing up your campaigns? Now you can verify email addresses directly inside Google Sheets with the mailfloss Email Verifier extension—no more switching tabs or manual work!
✅ Verify emails without leaving your spreadsheet
⚡ Process thousands of emails in seconds
🔍 Instantly filter out bad addresses
💡 Ready to clean up your email lists? Install the mailfloss Google Sheets extension today and say goodbye to bad emails!
Beehiiv is a powerful email marketing platform designed specifically for creators and publishers. Our new integration brings Instafloss’s real-time email verification directly into your beehiiv workflow, ensuring your email lists stay clean, accurate, and high-performing.
With the mailfloss beehiiv integration, you’ll get:
Instant email verification at the point of entry
Automatic typo correction
Automated unsubscribe, delete, and/or labels updating
Reduced bounce rates and improved email deliverability
Ready to supercharge your email list? Navigate to Integrations and click the Add Integration button to connect your beehiiv account and start optimizing your email list quality today. We can’t wait to hear how this integration helps streamline your email marketing efforts!
Our Click Funnels email verification integration is now available. Click Funnels is a powerful sales funnel builder that helps entrepreneurs turn visitors into customers. And with our integration, you get Instafloss real-time email verification, an automated typo-fixer, automated custom field updating, deleting, and more.
Feel free to connect your Click Funnels account by visiting Integrations and clicking on the Add Integration button to get started. We’re excited to hear your thoughts on the integration.
We’ve released a new API for our Integration Settings. The API is in beta and we are actively seeking feedback.
Right now you are able to add blacklist and whitelist options to any integration using this API - both in bulk and one at a time. We will add additional endpoints in the future based on your feedback. Please give it a try and let us know what you think.
We’re happy to announce that our Zapier integration is out of beta. It no longer requires an invite to use and can be found within the Zapier marketplace.
You can also find it directly in the mailfloss app by going to Plugins and selecting Zapier. Direct link here.
We’ve added the ability to register an account and log in using Azure AD authentication. No password is needed so this is generally a more secure method of logging in.
Azure AD Authentication works for personal Outlook addresses as well as Microsoft Azure AD business accounts.
If you already have an account registered with the same email address, the first time you try to log in using this method will link this authentication method with the account. And subsequent login attempts will succeed.
We’ve added the ability to register an account and log in using LinkedIn authentication. No password is needed so this is generally a more secure method of logging in.
LinkedIn authentication works by connecting your LinkedIn account with mailfloss.
If you already have an account registered with the same email address, the first time you try to log in using this method will link this authentication method with the account. And subsequent login attempts will succeed.
We’ve added the ability to register an account and log in using Google authentication. No password is needed so this is generally a more secure method of logging in.
Google Authentication works for personal Gmail addresses as well as Google Workspace business accounts.
If you already have an account registered with the same email address, the first time you try to log in using this method will link this authentication method with the account. And subsequent login attempts will succeed.
Many of you file uploaders often requested to keep the original data in the uploaded file and to append the mailfloss results to it. Well I’m happy to report that this is finally a reality for uploaded CSV files.
The generated appended file does take much longer to generate compared to just our report, but the option is there for those who want it.
You can initiate the process by visiting the Dashboard, clicking the “Export Emails” button and turning on the “Append results” option for the desired floss session.
Please note that this only works with CSV files and not Excel files.
We’ve added a category to detect if an email address failed Microsoft Exchange testing.
This category is extremely useful if you have many accept all domains in your email lists, as Microsoft Exchange is by far the largest email provider for businesses. With this new category, if the domain is using Microsoft Exchange there’s a good chance we can tell the difference between a real accept all address and a fake one.
This test is run by default through file upload and copy & paste. For our supported integrations, you can turn it on by setting your Aggressiveness Options to custom and selecting “failed exchange emails”, it is also included in the Aggressive setting.
One of our most requested options has finally arrived - custom decay protection schedules. Prior to this release, our decay protection would run once a month. Now, monthly is the default option, and in addition you can change the schedule to run weekly, twice a month, once every 2 months, 3 months, and 6 months. The schedule is also available on individual lists for some of our integrations.
To get started, go to the integration you wish to run a custom decay protection schedule on. Ensure Decay Protection is turned on, and then click the three vertical dots to set the desired schedule.
MailerLite has two versions, the classic version and the new. mailfloss now supports both. When you connect a new MailerLite account to mailfloss, the only difference now is an extra checkbox to indicate if the account is using MailerLite Classic or not.
We’ve updated our Klaviyo integration to use the new API endpoints, as the older API endpoints we were using are set to retire in 2024.
The migration is live and all Klaviyo accounts are now using these new endpoints. Please reach out if you have any questions or concerns regarding the migration.
Our Infusionsoft integration now supports custom fields updates. Previously, we relied on the tagging functionality, but we are migrating to custom fields as they are more appropriate for our purposes.
Custom field updating is available for use immediately on all Infusionsoft accounts subscribed to the Pro plan, as well as as an add-on to the Business and Lite plans.
Current customers using the tagging option are unaffected by this update, and are welcome to switch to custom fields updates instead.
We’re excited to announce the first version of our javascript widget.
Use this widget to embed on your forms, opt-ins, call-to-actions, popups, and so on.
The widget is especially useful if you don’t use a supported email service provider integration, as it allows for real-time verification at the point of entry.
Setup requires some technical knowledge and the ability to modify the HTML the widget will reside on.