Skip to content

// website builders and cms

Via API

Softr email verification with pingutil

Client portals and member directories built on Softr get signups from temp-mail and mistyped addresses, and those users then receive your workflow emails and count toward your user totals. Softr Workflows can fire on the User added trigger and call pingutil from a Run Custom Code step, then branch to update or remove the user. User added polls about once a minute, so this is cleanup shortly after signup, not a block on the signup form.

Where it connects: Softr Workflows, Softr Apps "User added" trigger with a Run Custom Code action

What goes wrong without it

  • Our Softr client portal has signups from people who clearly are not clients, all on disposable inboxes.
  • We pay per user on our plan and fake accounts are eating the seats.
  • Welcome emails from our workflow bounce and we only find out when someone complains they never got access.

What you can do with Softr and pingutil

  • Flag new users with bad addresses

    After the check, a branch writes status and reason to a field on the user's record in your users table, so an admin view can filter flagged accounts.

  • Hold welcome emails for invalid addresses

    Put the welcome email action on the branch for valid and risky results only, so the workflow never mails a dead inbox.

  • Spot business users in a B2B portal

    A second call to /v1/lookup returns category and company.name; save them on the user record to see which companies signed up.

Set it up

  1. 1

    Add a REST API integration with Base URL https://pingutil.com and an Authorization header of Bearer pk_live_your_key, so the key stays out of the code.

  2. 2

    Create a workflow with the Softr Apps "User added" trigger and select your app.

  3. 3

    Add Run Custom Code (JavaScript), map the new user's email to inputData.email, and attach the pingutil REST API integration to the step.

  4. 4

    Add Branches on the step output body.status: one path for invalid, one for everything else.

  5. 5

    On the invalid path, update the user's record (for example an Email status field) or remove them; on the other path, continue with your welcome actions.

Run Custom Code step (JavaScript, version 1.3.0)
// inputData.email is mapped from the User added trigger.
// The attached REST API integration (Base URL https://pingutil.com) adds the Authorization header.
const fallback = { status: 'unknown', reason: 'check_skipped', score: null, did_you_mean: null };

const timeout = new Promise((resolve) => setTimeout(() => resolve(null), 25000));
const call = (async () => {
  try {
    const res = await fetch('https://pingutil.com/v1/verify', {
      method: 'POST',
      body: { email: inputData.email },
    });
    return res.ok ? await res.json() : null; // 429 / 5xx: fail open
  } catch (e) {
    return null; // network error: fail open
  }
})();

const result = (await Promise.race([call, timeout])) || fallback;

return {
  status: result.status,
  reason: result.reason,
  score: result.score,
  did_you_mean: result.did_you_mean || '',
};

What to do with each result

pingutil resultAction in Softr
status: "invalid"Branch to update the user record as flagged, or remove the user.
status: "risky"Continue, and write the reason (accept_all, role_based) to the user record.
did_you_mean is setSend an admin notification with the suggested address.
status: "valid" or "unknown"Continue with welcome and onboarding actions.

Limits to plan for

  • The User added trigger polls about every minute and runs after the account exists, so a fake user can log in briefly before the workflow acts.
  • Run Custom Code requires Softr's Pro plan or above; fetch and integration-authenticated calls need step version 1.2.0 or later.
  • Each verified address counts toward pingutil's 300 a day per account (3,000 a month). Large imports of users will trigger the workflow for every one. Those are Free plan limits; Enterprise has custom limits.

Softr documentation

Softr is a trademark of its owner. This integration uses Softr's documented extension points; it is not an official Softr app.

Common questions

Can Softr block the signup before the user is created?
Not with the User added trigger, which fires after creation. If you build signup as a Softr form with the Submit form trigger, the workflow runs synchronously and can check the address before you create the user yourself.
Why not paste the API key into the code?
Softr recommends attaching an integration instead. The REST API integration sends the header for you and keeps the key out of the workflow definition and run details.

Stop bad addresses in Softr today

Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Softr setup will receive.