Sokko

Usa mailfloss con Sokko.

Conecta mailfloss y dile a Sokko qué hacer. Ejecuta las acciones que pides y reacciona a lo que ocurre, sin workflows ni código.
Funciona con más de 1.000 herramientas · Sin código
Acciones

Todo lo que Sokko puede hacer en mailfloss

Cada acción de mailfloss que Sokko puede ejecutar. Pídela en una frase y listo.

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.
Conéctate

En tu Slack en dos minutos.

Sin flujos que configurar. Activa las herramientas que ya usas y tu agente se pone a trabajar.
Añadir a Slack
1

Añade Sokko a Slack

Un clic desde el marketplace de Slack. Todo tu equipo tiene Sokko de una vez.
Gmail
Outlook
Yandex
Zoho Mail
Agent Mail
BlueFox Email
Bouncer
Bulk Email Checker
2

Conecta tus herramientas

Sokko funciona con más de 1000 apps y cualquier servidor MCP.
Martin
9:53 AM
@Sokko
¿Qué puedes hacer con mailfloss?
3

Pon a Sokko a trabajar

@menciona a Sokko en cualquier canal y arranca. Minutos, no un fin de semana.

Preguntas, respondidas.

Sokko es un asistente de IA que vive en tu Slack. Conecta tus apps, pide lo que necesitas en lenguaje natural y Sokko se encarga del trabajo por ti.

Regístrate en Sokko, pídele a Sokko que se conecte a mailfloss y aprueba la conexión cuando se te solicite. A partir de ahí puedes pedirle a Sokko que haga cosas en mailfloss cuando quieras.

No. No hay nada que crear ni configurar. Le pides a Sokko en Slack igual que se lo pedirías a un colega, y Sokko se encarga del resto.

Sí. Pídelo una vez y dile a Sokko cuándo repetirlo, como cada lunes a las 9 h, y se convierte en una rutina que se ejecuta sin ti.

Leer y actuar sobre los datos de mailfloss, y lanzar workflows cuando algo cambia. Dile a Sokko el resultado que quieres y se encarga del resto.

Sí. Sokko se conecta a más de 1.000 apps y a cualquier servidor MCP, así que puedes pedir tareas que abarquen mailfloss y el resto de tu stack en una sola petición.

¿Qué hará tu primer agente?

Crea un agente, conecta tus herramientas y asígnale una tarea. Tus primeros 3 días son gratis, con $5 en créditos de IA para empezar.