Skip to content

// website builders and cms

Via API

Bubble email verification with pingutil

Bubble apps that offer a trial or credits attract signups from throwaway inboxes, and every fake user costs workload units and skews your metrics. Because Bubble workflows run step by step, an API Connector action that asks pingutil about the address can sit before "Sign the user up" and gate it with an Only when condition. This one blocks at sign-up; no user is created when the check fails.

Where it connects: API Connector plugin call (Use as: Action) placed before "Sign the user up" in the signup workflow

What goes wrong without it

  • People create new accounts with temp-mail every week to reset their free credits in our Bubble app.
  • Our user table keeps growing but activation is flat, because most of the new users are fake.
  • Password reset emails bounce and Bubble support asked us to look at our sending reputation.

What you can do with Bubble and pingutil

  • Gate "Sign the user up" on the verdict

    Run the pingutil lookup action first, then add Only when Result of step 1's verdict is_spam is no to the signup step. Disposable and randomized addresses never become users.

  • Show a typo suggestion on the signup page

    Use a /v1/verify call instead and, when did_you_mean is not empty, show it in a text element so the user can fix jane@gmial.com before trying again.

  • Save the category on the user

    Store category (company, free, educational) on the User thing right after signup, so onboarding and pricing pages can treat business signups differently.

Set it up

  1. 1

    Install the API Connector plugin, add an API named pingutil, and set Authentication to "Private key in header" with key name Authorization and value Bearer pk_live_your_key.

  2. 2

    Add a call named screen email, Use as: Action, Data type JSON, method POST, URL https://pingutil.com/v1/lookup, with the JSON body below and email as a non-private parameter.

  3. 3

    Check "Include errors in response and allow workflow actions to continue", give the email parameter a sample value, and initialize the call.

  4. 4

    In the signup button workflow, add Plugins → pingutil - screen email as step 1 with email = the email input's value.

  5. 5

    On "Sign the user up", add Only when Result of step 1's verdict is_spam is no; add a separate step that shows an error when it is yes.

API Connector call body (POST https://pingutil.com/v1/lookup)
{
  "input": "<email>",
  "skip_enrichment": true
}

What to do with each result

pingutil resultAction in Bubble
verdict.is_spam: yesSkip "Sign the user up" and show "Please use a permanent email address".
verdict.low_trust: yesSign the user up and set a needs_review field on the User.
category: "company"Save category and domain on the User for onboarding or sales routing.
Error returned (429, 5xx, timeout)Treat as not spam so the signup continues; Bubble exposes the error object when errors are included in the response.

Limits to plan for

  • Fast mode classifies the address without an SMTP check; a dead mailbox at a real provider still passes. Use /v1/verify (field email) if you need mailbox-level results and can accept a few seconds of wait.
  • Without "Include errors in response", a failed call stops the workflow, which would block real signups during an outage. Leave it checked and re-initialize after changing it.
  • API Connector actions run on Bubble's server; the key stays private only with an authentication method like "Private key in header".

Bubble documentation

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

Common questions

Can I call pingutil straight from the browser in Bubble?
Do not. A browser call would need the key in the page. Keep the call server-side through the API Connector with the key in a private header.
Should the condition use verdict.is_spam or category?
verdict.is_spam. It covers disposable domains and randomized addresses on real providers. category alone misses gibberish addresses at gmail.com.

Stop bad addresses in Bubble 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 Bubble setup will receive.