DEV Community

Cover image for Stop writing glue code for email verification: MailValid is now on Integrately
MailValid.io
MailValid.io

Posted on AI-assisted

Stop writing glue code for email verification: MailValid is now on Integrately

A lot of "verify this email" code isn't in a signup form at all. It's glue: a small handler that receives a webhook from a form tool or an ad platform, calls a verification API, and writes the result into a CRM. Someone has to host it, watch it and fix it when a field name changes.

MailValid is now on Integrately, so that glue can be a no-code automation instead. Disclosure: I work at MailValid.

What the action is

The MailValid app on Integrately has one action, Verify Email in MailValid, which Integrately describes as "Verify a single email address for deliverability and validity". There are no MailValid triggers; it sits between another app's trigger and whatever happens next.

Trigger (form, ad lead, sheet row, CRM contact)
  → Verify Email in MailValid
  → Update / tag / route the record
Enter fullscreen mode Exit fullscreen mode

It does the same job as this request to the REST API:

curl -X POST https://mailvalid.io/api/v1/verify/single \
  -H "X-API-Key: $MAILVALID_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "jane@company.com"}'
Enter fullscreen mode Exit fullscreen mode

The API response includes a status that's one of valid, invalid, catch_all, unknown or do_not_mail, plus flags like is_disposable and is_role_based. All five statuses and their sub-reasons are in the status docs. When you test the step in Integrately, its output panel shows which fields you can map into the next step.

When the no-code step is the better choice

  • The data already lives in SaaS tools. Integrately has triggers like Lead is created in Facebook Lead Ads, Form is submitted in Typeform, Spreadsheet row is created in Google Sheets and Contact is created in HubSpot. You don't need an endpoint to receive them.
  • Someone else owns the workflow. A marketer can change the routing (tag, list, CRM property) without a deploy.
  • You'd otherwise run a server for one handler. No hosting, no signature checks, no retries to write.

When to keep it in code

  • You need to block the address before submit. Integrately runs after the event, so it can't stop a typo while the user is still on the form. Do that in your app. Here's a signup form guide.
  • You're verifying an existing list. The action checks one address at a time. For a list, use the bulk endpoint (POST /api/v1/verify/bulk, up to 10,000 emails per job on paid plans) or upload a CSV in the dashboard.
  • You need custom logic. Branching on confidence_score thresholds or combining several flags is easier in code.

Handling the statuses

Whichever route you take, the same rule set works for most pipelines:

invalid      → drop from campaigns
do_not_mail  → keep out of marketing (disposable, role-based or past complaint)
valid        → continue
catch_all    → keep, but don't treat as confirmed
unknown      → keep, retry later (unknown results don't use credits)
Enter fullscreen mode Exit fullscreen mode

Plan limits worth knowing

  • Integrately's free plan has 100 tasks a month and single-step automations. "Verify, then write the result somewhere" is two steps, so it needs a paid plan with multiple steps (Starter is listed at $19.99/month billed annually, for 2,000 tasks).
  • Facebook Lead Ads and Webhooks are marked Premium apps on Integrately.
  • On the MailValid side, each definitive result uses one credit; unknown is free. New accounts get 100 free credits.

The launch write-up with five ready-to-build automations is on our blog: MailValid Is Now on Integrately.

If you've replaced a webhook handler with a no-code step (or gone the other way), I'd like to hear why in the comments.

Top comments (0)