🎬 Introducing BillionVerify Video Tutorials: short guides to verifying emails, free tools, and cleaning leads.Watch videos
← All Developer Tools Workflows
BillionVerifyPagerduty

Detect and route cybersecurity threats with SIEM, Slack, email and PagerDuty

Pull contacts, verify each address with BillionVerify, and continue to PagerDuty — only deliverable addresses get through.

Why verify before the send

Sending to invalid, risky, catch-all, or disposable addresses spikes your bounce rate and erodes sender reputation. A verification gate before the PagerDuty step removes that risk automatically — only deliverable addresses continue, the rest are flagged.

The workflow

BillionVerify — verification sits right before the send.

+8
n8n steps
+9
n8n steps

Node by node

  1. 1
    Schedule Trigger - Every 15 MinutesTrigger· n8n

    Starts the workflow — on a schedule, a webhook, or manually while you test.

  2. 2
    Fetch Network LogsSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  3. 3
    Fetch Vulnerability Scan ResultsSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  4. 4
    Fetch Threat Intelligence FeedSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  5. 5
    Merge All Threat DataSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  6. 6
    Analyze & Detect ThreatsSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  7. 7
    Check Threat SeverityLogic· n8n

    Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.

  8. 8
    Send Slack Alert - CriticalSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  9. 9
    Verify Email (BillionVerify)Verify· billionverify

    The BillionVerify node verifies the address — status (valid / invalid / risky / catch-all / role / disposable), is_deliverable, and a confidence score — before anything is sent.

  10. 10
    Log Medium/Low ThreatsSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  11. 11
    Create PagerDuty IncidentSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  12. 12
    IF deliverableLogic· n8n

    Branches on the verification result: only deliverable addresses continue to the send; the rest are skipped and flagged.

  13. 13
    Store in DatabaseSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  14. 14
    Merge All PathsSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  15. 15
    Send Email Alert - DetailedSend· n8n

    Sends only to verified, deliverable addresses. Swap in your own provider node if you send elsewhere.

  16. 16
    Generate Summary ReportSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  17. 17
    Create Security TicketSource· n8n

    Provides or transforms the contact data flowing through the workflow.

  18. 18
    Send Summary to Monitoring ChannelSource· n8n

    Provides or transforms the contact data flowing through the workflow.

Workflow JSON

Copy or download this workflow, then import it in n8n (Workflows → Import from File / Paste). Install the BillionVerify community node first, then add your API key credential.

verify-emails-in-pagerduty.json24 KB · n8n workflow

When to use this

  • Cleaning a list before a PagerDuty send or sync.
  • Protecting PagerDuty deliverability and sender reputation.
  • Keeping bounce rates low so your sending is never throttled.

FAQ

Why verify before sending in PagerDuty?

Verifying first keeps your bounce rate low, which protects your sender reputation and your results.

How do I import this workflow?

Download the JSON, then in n8n go to Workflows → Import from File (or paste it). Install the BillionVerify community node and add your API key credential.

What happens to risky or catch-all addresses?

They are routed to the false branch and excluded from the send. You decide whether to retry, review, or drop them.

Add verification to your workflow

Create a free account, grab your API key, and stop bounces before they happen.

Get started free