Skip to content

// support, community and events

Via API

Fidiora email verification with pingutil

Fidiora answers support questions with AI, captures leads from buying-intent conversations and hands the rest to your team, and all of that ends in someone replying by email. When the address is mistyped or disposable, the follow-up bounces and the lead is gone. Fidiora can send events such as captured leads and handoffs to another system by webhook, so your endpoint can verify the customer email with pingutil and tell sales or the agent before they write back.

Where it connects: Fidiora webhooks (events such as a captured lead or a handoff to your team) sent to your own endpoint

What goes wrong without it

  • Fidiora captured a hot lead from the chat, sales emailed them the next morning, and the reply bounced because of a typo.
  • People ask the chat for a quote with a throwaway address, and the lead lands in our CRM next to real buyers.
  • An agent spends twenty minutes on a handed-off conversation, then finds out the customer's email does not exist.

What you can do with Fidiora and pingutil

  • Verify captured leads before they reach the CRM

    Fidiora's lead capture routes buying-intent conversations to a sales stage, your CRM or a team channel. Put a webhook receiver in that path that runs /v1/verify on the lead email and forwards it with email_status, or holds back disposable and dead addresses.

  • Warn the agent on a handoff

    When a conversation is handed to a human, verify the customer email and post the result to the team channel, including did_you_mean, so the agent confirms the address in the chat before the conversation ends.

  • Give sales the company behind the lead

    A /v1/lookup on a company address returns category and, for company domains, a company profile (industry, size, location) that sales can read before the first reply.

Set it up

  1. 1

    Create a pingutil API key in your dashboard and store it as PINGUTIL_KEY on the server that will receive the webhook.

  2. 2

    Deploy the Express handler below at a public HTTPS URL that includes a long random token, and set FIDIORA_HOOK_TOKEN to the same value.

  3. 3

    In Fidiora, send the events you care about (captured leads, handoffs) to that URL. The integrations overview lists webhooks, the API and Zapier or Make as the ways to connect; if you do not see a webhook setting in your workspace, ask Fidiora support at support@fidiora.com.

  4. 4

    Trigger a test lead with your own address and check the logged payload: confirm which field holds the customer email and whether deliveries are signed, then tighten the handler to that field.

  5. 5

    Point SLACK_WEBHOOK_URL (or your CRM endpoint) at the place your team already reads, and fire a lead with a disposable address to see the warning.

Express receiver for Fidiora lead and handoff events
import express from 'express';

const app = express();
app.use(express.json({ limit: '256kb' }));

// Fidiora's docs do not publish the payload schema, so find the first email-looking value.
// Once you have seen a real delivery, replace this with the exact field.
function findEmail(v: unknown): string | null {
  if (typeof v === 'string') return /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(v.trim()) ? v.trim() : null;
  if (v && typeof v === 'object') for (const x of Object.values(v)) { const e = findEmail(x); if (e) return e; }
  return null;
}

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

async function notify(text: string) {
  await fetch(process.env.SLACK_WEBHOOK_URL!, {
    method: 'POST',
    headers: { 'content-type': 'application/json' },
    body: JSON.stringify({ text }),
  });
}

app.post('/webhooks/fidiora/:token', async (req, res) => {
  if (req.params.token !== process.env.FIDIORA_HOOK_TOKEN) return res.sendStatus(404);
  res.sendStatus(200); // answer first, verification can take seconds

  const email = findEmail(req.body);
  if (!email) return;

  const [v, lookup] = await Promise.all([
    pingutil('/v1/verify', { email }, 25000),
    pingutil('/v1/lookup', { input: email }, 10000),
  ]);
  if (!v) return; // pingutil unavailable: leave the lead as it is

  if (v.status === 'invalid' || v.reason === 'disposable_domain') {
    const hint = v.did_you_mean ? ' Did they mean ' + v.did_you_mean + '?' : '';
    return notify('Fidiora lead ' + email + ' will not receive email (' + v.reason + ').' + hint);
  }

  const company = lookup?.category === 'company' && lookup.company?.name ? ' at ' + lookup.company.name : '';
  await notify('Fidiora lead ' + email + company + ': ' + v.status + ' (' + v.reason + ').');
});

app.listen(3000);

What to do with each result

pingutil resultAction in Fidiora
reason: 'disposable_domain'Hold the lead out of the CRM and tell the team it came from a throwaway address.
status: 'invalid' with did_you_meanPost the suggested address so the agent can confirm it with the customer in the chat.
status: 'invalid' without did_you_meanFlag the lead as unreachable by email; follow up in the chat or another channel.
status: 'risky' or 'unknown'Pass the lead on with the status visible. Catch-all company domains return risky, never valid.
category: 'company' with a company profileAdd the company name and industry to the lead so sales has context before replying.

Limits to plan for

  • Fidiora's public docs name webhooks, the API and Zapier or Make as connection methods and list captured leads and handoffs as events, but they do not publish event names, payload fields, signing or an API to tag a lead. Check those in your workspace or with Fidiora support before you rely on them; the snippet posts results to your team channel instead of writing back to Fidiora.
  • Verification can take several seconds on slow mail servers, so answer the webhook with 200 first and verify afterwards.
  • Each lead costs one verification and one lookup. The Free plan allows 300 verifications a day (3,000 a month), 2,000 lookups a day and 50 new company profiles a day; Enterprise has custom limits.

Fidiora documentation

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

Common questions

Does Fidiora verify emails with pingutil on its own?
Not as a built-in setting today. You connect the two through a webhook receiver like the one above, or through Zapier or Make, which Fidiora lists as supported automation tools.
Can I use Zapier instead of my own server?
Yes. Fidiora lists captured leads and escalations among the events Zapier can start from. Add a Webhooks by Zapier step that POSTs the email to https://pingutil.com/v1/verify with your Bearer key, then filter on status before the CRM step.

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