Skip to content

// website builders and cms

Via API

Circle email verification with pingutil

Open Circle communities attract spam accounts and members on throwaway inboxes, and they show up in member directories, digests and your member count. Circle's automation workflows can send a Joined community event to a webhook, your endpoint verifies the member's email with pingutil, and the Admin API v2 tags the member or deactivates them. The member has already joined when this runs, so it is cleanup, not a gate.

Where it connects: Circle automation workflow, Joined community trigger with the Send to webhook action, plus Admin API v2 member tags

What goes wrong without it

  • Spam accounts join our Circle community and post links before a moderator even sees them.
  • Our weekly digest goes to a growing list of members on disposable inboxes.
  • Moderators spend time reviewing every new member profile by hand.

What you can do with Circle and pingutil

  • Tag members whose email fails

    Apply a member tag such as email-flagged through POST /api/admin/v2/tagged_members, then filter by that tag in the members list or audience rules.

  • Remove members on disposable domains

    Look up the member with GET /api/admin/v2/community_members/search?email= and deactivate them with DELETE /api/admin/v2/community_members/{id}. Posts are kept and re-adding the email restores membership.

  • Cut the moderator review queue

    Only members tagged by the check need a human look, instead of every new join.

Set it up

  1. 1

    Create a member tag (for example email-flagged) in Circle and note its ID; get an Admin API token from Settings → Developers → Tokens.

  2. 2

    Create an automation workflow with the Joined community trigger and the Send to webhook action pointing at your endpoint, with a secret token in the URL query string.

  3. 3

    Click Test webhook and use Show test data output to confirm which field carries the member's email.

  4. 4

    In the endpoint, check the token, answer 200, verify the email with pingutil, and tag or deactivate the member through the Admin API v2.

  5. 5

    Activate the workflow and join with a disposable address to confirm the tag appears.

Flask endpoint for Circle Send to webhook
import hmac
import os
import threading

import requests
from flask import Flask, abort, request

app = Flask(__name__)
CIRCLE = "https://app.circle.so/api/admin/v2"
CIRCLE_HEADERS = {"Authorization": f"Bearer {os.environ['CIRCLE_API_TOKEN']}"}


def find_email(data):
    # Circle does not publish the payload schema: use the path shown in "Show test data output".
    if isinstance(data, dict):
        for key, value in data.items():
            if "email" in key.lower() and isinstance(value, str) and "@" in value:
                return value
            found = find_email(value)
            if found:
                return found
    elif isinstance(data, list):
        for item in data:
            found = find_email(item)
            if found:
                return found
    return None


def verify(email):
    try:
        res = requests.post(
            "https://pingutil.com/v1/verify",
            json={"email": email},
            headers={"Authorization": f"Bearer {os.environ['PINGUTIL_KEY']}"},
            timeout=25,
        )
        return res.json() if res.ok else None  # 429 / 5xx: fail open
    except requests.RequestException:
        return None  # timeout or network error: fail open


def screen(email):
    result = verify(email)
    if not result or result["status"] != "invalid":
        return
    requests.post(
        f"{CIRCLE}/tagged_members",
        json={"member_tag_id": int(os.environ["CIRCLE_FLAG_TAG_ID"]), "user_email": email},
        headers=CIRCLE_HEADERS,
        timeout=10,
    )


@app.post("/webhooks/circle")
def circle_webhook():
    if not hmac.compare_digest(request.args.get("token", ""), os.environ["CIRCLE_WEBHOOK_TOKEN"]):
        abort(401)
    email = find_email(request.get_json(silent=True) or {})
    if email:
        threading.Thread(target=screen, args=(email,), daemon=True).start()
    return "", 200

What to do with each result

pingutil resultAction in Circle
status: "invalid", reason disposable_domainTag email-flagged, or deactivate with DELETE /community_members/{id}.
status: "invalid", reason mailbox_not_found or no_mxTag email-flagged so moderators can follow up.
status: "risky"Optionally apply a separate review tag; no removal.
status: "valid", "unknown" or no responseDo nothing; the member stays as joined.

Limits to plan for

  • The Joined community trigger fires once the member has joined and confirmed their profile, so a spam account can act before the check finishes.
  • Circle limits the Send to webhook action to certain plans, and Admin API v2 access depends on community eligibility; check both before building.
  • Circle does not document a signature for workflow webhooks, so protect the endpoint with a long random token and HTTPS.

Circle documentation

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

Common questions

Deactivate or delete a flagged Circle member?
Deactivate. DELETE /community_members/{id} keeps their posts and lets the same email rejoin. The separate delete_member call permanently removes the member and their content, which is hard to undo if the check was wrong.
Can I use Zapier instead of a workflow webhook?
Yes. Circle's Zapier integration has a New Member Added trigger; a Code or Webhooks step can call pingutil and a later step can tag the member.

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