Audit digital identities with Apify BreachHound and PDF.co
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs when someone submits an n8n form (“Digital Identity Audit”). Along the way it connects Apify (community). It also calls api.pdf.co over HTTP.
How it runs
Trigger: When someone submits an n8n form (“Digital Identity Audit”).
- Set Fields (Edit Fields (Set)): sets 3 fields: email, onlyUsed, useResidentialProxy
- Run an Actor (Apify): uses Apify
- Get dataset items (Apify): work with datasets
- Data Extraction (Code): runs custom JavaScript code
- Convert to HTML (Code): runs custom JavaScript code
- HTML to PDF (HTTP Request): calls api.pdf.co (POST)
- HTTP Request: calls an HTTP API
Services it uses
HTTP calls to: api.pdf.co
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @apify/n8n-nodes-apify is verified or supports 3.0 (used in Run an Actor, Get dataset items).
Nodes used (5)
- n8n Form Trigger
n8n-nodes-base.formTrigger - Apify
@apify/n8n-nodes-apify.apify - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code
From the author
Quick overview This workflow starts from an n8n form submission, runs the BreachHound actor on Apify to discover where an email address is registered, then summarizes the results into an HTML audit report and converts it to a downloadable PDF using PDF.co.…