Use mailfloss with Sokko.
Connect mailfloss and tell Sokko what to do. It runs the actions you ask for and reacts to what happens. No workflows, no code.
Works with 1,000+ tools · No code required
Actions
Everything Sokko can do in mailfloss
Every mailfloss action Sokko can run. Ask for one in a sentence and it's done.
Cancel Batch Verification
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.
Check API Key
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.
Create Batch Verification
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.
Erase Verification Records
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.
Get Account
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.
Get Batch Verification Results
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.
Get Batch Verification Status
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.
Get Verification Job
Return one verification job and its complete verdict breakdown. Results are null until completion and include all per-reason counters when present.
Get Organization
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.
Get Usage Report
Return verification usage for a UTC calendar period, optionally scoped to one ESP connection except for lifetime reports. Lifetime reports contain only the authoritative total; their range, status counts, and reason counts are null.
List Verification Jobs
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 Email
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.
Get connected
Live in your Slack in two minutes.
No workflows to wire up. Turn on the tools you already use, and your agent gets to work.
Add to Slack
1
Add Sokko to Slack
One click from the Slack marketplace. Your whole team gets Sokko at once.
2
Connect your tools
Sokko works with 1,000+ apps and any MCP server.
Martin
9:53 AM
@Sokko
What can you do with mailfloss?
3
Put Sokko to work
@mention Sokko in any channel and it gets going. Minutes, not a weekend.
Questions, answered.
Sokko is an AI assistant that lives in your Slack. Connect your apps, ask for what you need in plain language, and Sokko takes the work off your plate.
Sign up to Sokko, ask Sokko to connect to mailfloss, and approve the connection when prompted. From then on you can ask Sokko to do things in mailfloss whenever you need.
No. There's nothing to build or configure. You ask Sokko in Slack the same way you'd ask a colleague, and Sokko handles the rest.
Yes. Ask once and tell Sokko when to repeat it, like every Monday at 9am, and it becomes a routine that runs without you.
Read and act on data in mailfloss, and trigger workflows when something changes there. Tell Sokko the outcome you want and it handles the rest.
Yes. Sokko connects to 1,000+ apps and any MCP server, so you can ask for tasks that span mailfloss and the rest of your stack in a single request.