Skip to content

// support, community and events

Via API

Zendesk email verification with pingutil

Zendesk creates an end user for every new requester, and a mistyped or dead address means every public reply on their tickets bounces while the customer waits. A webhook on zen:event-type:user.created sends each new user to your endpoint, pingutil verifies the address, and the result goes back on the user as a tag that triggers, views and agents can see.

Where it connects: Zendesk webhook subscribed to the zen:event-type:user.created event, then the Tags API on the user

What goes wrong without it

  • The customer filled in the web form as john@outlok.com and every reply we send bounces. The ticket sits there until they open a second one, angrier.
  • Agents have no idea a requester address is bad until the bounce notification lands.
  • Spam requesters on throwaway domains open tickets that we answer in good faith.

What you can do with Zendesk and pingutil

  • Flag requesters whose replies will bounce

    Users with an invalid result get an email_invalid tag. Build a view of open tickets from tagged requesters so an agent can reach them another way, or use the did_you_mean suggestion to correct the address.

  • Deprioritize throwaway requesters

    A disposable_domain result adds email_disposable. A trigger can lower priority or route those tickets to a spam review group instead of the main queue.

  • Spot business customers

    A /v1/lookup call with skip_enrichment: true returns category in milliseconds. Tag company-domain requesters as work_email so triggers can route them to a priority group.

Set it up

  1. 1

    Create a pingutil API key and set it as PINGUTIL_KEY on your webhook receiver.

  2. 2

    Make sure user tagging is turned on in Zendesk Admin Center so user tags are stored.

  3. 3

    In Admin Center, go to Apps and integrations, Webhooks, and create a webhook that subscribes to the zen:event-type:user.created event and points at your endpoint. Copy its signing secret.

  4. 4

    Deploy the handler below with ZENDESK_SUBDOMAIN, ZENDESK_EMAIL and ZENDESK_API_TOKEN set. It checks the webhook signature, answers right away and adds tags through the Tags API.

  5. 5

    Create a test end user with a mistyped address and confirm the tag shows up on the user profile.

  6. 6

    Add a view or trigger that uses the new tags.

Express handler for zen:event-type:user.created
import express from 'express';
import crypto from 'node:crypto';

const app = express();
const ZD = 'https://' + process.env.ZENDESK_SUBDOMAIN + '.zendesk.com/api/v2';
const auth = 'Basic ' + Buffer.from(process.env.ZENDESK_EMAIL + '/token:' + process.env.ZENDESK_API_TOKEN).toString('base64');

async function verify(email: string) {
  try {
    const res = await fetch('https://pingutil.com/v1/verify', {
      method: 'POST',
      headers: { authorization: 'Bearer ' + process.env.PINGUTIL_KEY, 'content-type': 'application/json' },
      body: JSON.stringify({ email }),
      signal: AbortSignal.timeout(30000),
    });
    return res.ok ? await res.json() : null; // fail open on 429 / 5xx
  } catch {
    return null;
  }
}

app.post('/webhooks/zendesk', express.raw({ type: 'application/json' }), async (req, res) => {
  const ts = req.get('X-Zendesk-Webhook-Signature-Timestamp') ?? '';
  const sig = crypto.createHmac('sha256', process.env.ZENDESK_WEBHOOK_SECRET!).update(ts + req.body.toString('utf8')).digest('base64');
  if (sig !== req.get('X-Zendesk-Webhook-Signature')) return res.sendStatus(401);
  res.sendStatus(200);

  const event = JSON.parse(req.body.toString('utf8'));
  if (event.type !== 'zen:event-type:user.created' || !event.detail.email) return;

  const v = await verify(event.detail.email);
  if (!v) return; // pingutil unavailable: no tag, nothing blocked

  const tags: string[] = [];
  if (v.reason === 'disposable_domain') tags.push('email_disposable');
  else if (v.status === 'invalid') tags.push('email_invalid');
  else if (v.status === 'risky') tags.push('email_risky');
  if (v.did_you_mean) tags.push('email_typo');
  if (tags.length === 0) return;

  await fetch(ZD + '/users/' + event.detail.id + '/tags', {
    method: 'PUT', // adds tags without removing existing ones
    headers: { authorization: auth, 'content-type': 'application/json' },
    body: JSON.stringify({ tags }),
  });
});

app.listen(3000);

What to do with each result

pingutil resultAction in Zendesk
status: 'invalid' (mailbox_not_found, no_mx)Tag email_invalid and surface the requester in a view so an agent contacts them another way.
did_you_mean is not nullTag email_typo. An agent can confirm the suggestion with the customer and update the user identity.
reason: 'disposable_domain'Tag email_disposable and let a trigger route the ticket to a spam review group.
status: 'risky' (accept_all)Tag email_risky. Replies will probably arrive but a bounce is possible; no action on the ticket.
status: 'unknown'Leave the user untagged. Unknown means the server would not answer, not that the address is bad.

Limits to plan for

  • User tags only work when user tagging is enabled in your Zendesk account.
  • The webhook fires after the user exists, so the first auto-reply may already have gone out before the tag lands.
  • pingutil verifies up to 300 addresses per account per day (3,000 a month); high-volume help desks should verify only end users who open tickets through channels where the address is typed by hand. Those are Free plan limits; Enterprise has custom limits.

Zendesk documentation

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

Common questions

Why use a user event instead of a ticket trigger?
An address only needs one check. The user.created event fires once per new requester, while ticket triggers would re-check the same customer on every ticket and burn your daily verification budget.
Does pingutil send anything to the customer?
No. The SMTP check stops before any message is sent, so the requester never sees a test email.

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