// support, community and events
Via APIFront email verification with pingutil
Front teams answer inbound email and form submissions from a shared inbox, and contact-form messages often carry a reply-to address that was mistyped or never existed. An application webhook on inbound_received sends each new message to your endpoint, pingutil verifies the contact handle, and your code tags the conversation and leaves an internal comment for the team.
Where it connects: Front application webhook on the inbound_received event, then the Core API (add conversation tag, add comment)
What goes wrong without it
- Website form messages land in Front with a reply address that bounces the moment we answer.
- We spend shared-inbox time on temp-mail senders who were never going to read our reply.
- Nobody knows a contact is unreachable until the delivery failure shows up in the thread.
What you can do with Front and pingutil
Comment on unreachable senders
An invalid result posts an internal comment with the reason and any did_you_mean suggestion, visible to teammates right in the conversation.
Tag and route throwaways
Disposable-domain senders get a tag. A Front rule on that tag can archive the conversation or move it to a low-priority inbox.
Flag business senders
A fast /v1/lookup with skip_enrichment: true tells you whether the sender uses a company domain or free webmail, so a tag can route business inquiries to sales.
Set it up
- 1
Create a pingutil API key (PINGUTIL_KEY) and a Front API token with permission to tag and comment on conversations (FRONT_TOKEN).
- 2
Create tags in Front for email-invalid, email-disposable and email-risky, and note their tag ids.
- 3
In Front, go to Settings, Developers, create an app, add the Application webhooks feature with your endpoint URL and subscribe to inbound_received. Copy the app signing key.
- 4
Deploy the handler below. It answers the x-front-challenge validation request, checks the x-front-signature header, then verifies the sender after acknowledging.
- 5
Send a test email from a disposable address to a connected inbox and confirm the tag and comment appear.
import express from 'express';
import crypto from 'node:crypto';
const app = express();
const FRONT = 'https://api2.frontapp.com';
const headers = { authorization: 'Bearer ' + process.env.FRONT_TOKEN, 'content-type': 'application/json' };
const TAGS: Record<string, string> = {
invalid: process.env.TAG_INVALID_ID!,
disposable: process.env.TAG_DISPOSABLE_ID!,
risky: process.env.TAG_RISKY_ID!,
};
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/front', express.raw({ type: 'application/json' }), async (req, res) => {
const ts = req.get('x-front-request-timestamp') ?? '';
const sig = crypto.createHmac('sha256', process.env.FRONT_SIGNING_KEY!).update(ts + ':' + req.body.toString('utf8')).digest('base64');
if (sig !== req.get('x-front-signature')) return res.sendStatus(401);
const challenge = req.get('x-front-challenge');
if (challenge) return res.json({ challenge }); // validation request when saving the URL
res.sendStatus(200); // Front times out after 5 seconds, so answer before verifying
const event = JSON.parse(req.body.toString('utf8'));
if (event.type !== 'inbound_received') return;
const convo = event.payload.conversation;
const email = convo.recipient?.handle;
if (!email || !email.includes('@')) return;
const v = await verify(email);
if (!v || v.status === 'valid' || v.status === 'unknown') return;
const tag = v.reason === 'disposable_domain' ? 'disposable' : v.status === 'invalid' ? 'invalid' : 'risky';
await fetch(FRONT + '/conversations/' + convo.id + '/tags', { method: 'POST', headers, body: JSON.stringify({ tag_ids: [TAGS[tag]] }) });
let body = 'pingutil: sender address is ' + v.status + ' (' + v.reason + ').';
if (v.did_you_mean) body += ' Did they mean ' + v.did_you_mean + '?';
await fetch(FRONT + '/conversations/' + convo.id + '/comments', { method: 'POST', headers, body: JSON.stringify({ body }) });
});
app.listen(3000);What to do with each result
| pingutil result | Action in Front |
|---|---|
| status: 'invalid' | Add the email-invalid tag and an internal comment so nobody replies into a bounce. |
| did_you_mean is not null | The comment includes the suggested address; a teammate can reply to it after confirming. |
| reason: 'disposable_domain' | Add the email-disposable tag; a Front rule on the tag can archive or move the conversation. |
| status: 'risky' | Add the email-risky tag and reply as normal. |
| category: 'company' from /v1/lookup | Tag as a business inquiry and route to the sales inbox with a rule. |
Limits to plan for
- Front times out webhook requests after 5 seconds and retries up to three times, so acknowledge first and verify afterwards.
- inbound_received fires for every inbound message, not only new conversations. Skip contacts you already checked, or the same sender burns the 300 verifications per day (3,000 a month) account default. Those are Free plan limits; Enterprise has custom limits.
- Mailing lists, notification senders and noreply addresses will often come back risky or invalid; filter them out by inbox or rule if they create noise.
Front documentation
Front is a trademark of its owner. This integration uses Front's documented extension points; it is not an official Front app.
Common questions
- Can I use a Front rule webhook instead of an app?
- Yes, rules have a Send to webhook action and you can scope it to specific inboxes. The application webhook shown here adds a signature header and a documented validation step, which makes the endpoint easier to secure.
- Does pingutil read the message content?
- No. Only the sender address is sent to pingutil.
Stop bad addresses in Front 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 Front setup will receive.