mailfloss provides email verification APIs for checking individual addresses and processing asynchronous verification batches.
Cancel a pending or in-progress batch verification job. This irreversible operation stops remaining work and re-credits unprocessed emails; it is a no-op if the job has already completed. Composio generates an idempotency key when omitted and preserves it for retries within this execution. Reuse a caller-supplied key for the same cancellation across separate calls.
Verify that the connected Mailfloss API key is valid. Uses the connection's Bearer credential and does not accept credentials, request widget tokens, or return signed-proof fields.
Submit email addresses for asynchronous batch verification and return the job ID. Optionally request a completion webhook instead of polling. This billable action can fail with 402 insufficient_credits. Composio generates an idempotency key when none is supplied, so internal retries reuse the same key and email list. Separate action calls replay the cached response only when the caller reuses that key with identical emails; changing the list fails with 422, while a concurrent same-key request can fail with 409.
Permanently erase stored verification records for the supplied email addresses. This destructive data-privacy operation is irreversible; erased records cannot be recovered. Addresses with no stored records are a successful no-op. The body contains only the documented emails array. Composio generates an idempotency key when omitted and preserves it for retries within this execution.
Return the authenticated Mailfloss account holder's identity, contact details, security posture, notification preferences, and signup time. This read does not expose API credentials or two-factor secrets.
Return one cursor-controlled page of stored batch results after organization floss-setting overrides. These statuses and reasons can differ from Verify Email's raw verdict for the same address; fetching stored results is not documented as consuming verification credits.
Read an asynchronous batch verification job's state and available counters. Polling is not documented as consuming verification credits; authentication, policy, not-found, rate-limit, and server responses remain errors rather than job states.
Return the authenticated Mailfloss organization's plan, credit balances, current-period usage, trial state, account status, and feature entitlements. This is a read-only view and does not expose API or billing credentials.
Return verification usage for a UTC calendar period, optionally scoped to one ESP connection. Lifetime reports contain only the authoritative total; their range, status counts, and reason counts are null.
Return one verification job and its complete verdict breakdown. Results are null until completion and include all per-reason counters when present.
Return one page of the organization's verification-job history, newest first, with optional source and lifecycle filters. Completed jobs include verdict totals; use Get Job for the full per-reason breakdown.
Verify one email address and return Mailfloss's raw engine verdict without organization floss-setting overrides. passed means safe to send, undeliverable is a hard failure, risky covers role, disposable, bounced, or complained addresses, and unknown includes accept-all addresses and transient SMTP failures. relay and gibberish are annotations and do not alter the verdict. Each successful call consumes one verification credit; a depleted balance fails with 402 insufficient_credits, so do not retry billable failures blindly.
The mailfloss integration connects your Dench AI CRM directly to mailfloss, so agents can read and act on your mailfloss data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
12 actions are available for agents to invoke on your behalf. Every call runs through mailfloss's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find mailfloss and click Connect — you'll authorize access through mailfloss's own sign-in flow. No API keys or code required.
Ask an agent to use mailfloss in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench mailfloss integration connects your AI CRM to mailfloss, so AI agents can work with your mailfloss data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The mailfloss integration currently exposes 12 actions, including Cancel Batch Verification, Check API Key, Create Batch Verification, Erase Verification Records, Get Account, and Get Batch Verification Results. Agents invoke them on your behalf from chat or from automations.
No. You connect mailfloss from your Dench workspace using mailfloss's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through mailfloss's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the mailfloss connection from your workspace settings at any time.