Home/Integrations/n8n
Document fraud checks inside your n8n canvas
Connect TamperCheck to n8n with HTTP Request nodes, webhooks, and AI Agent steps. When a file lands in your pipeline — from email, cloud storage, a form, or an internal system — n8n sends it to TamperCheck and routes the verdict to Slack, your CRM, a database, or the next step in the workflow. Self-host n8n or use n8n Cloud; TamperCheck stays API-first either way.
Why n8n
Document fraud detection where your team already works
Fits your existing automations — n8n already connects your stack. TamperCheck slots in as one node between intake and decisioning, without a separate review UI.
See every step — n8n's execution log shows exactly what was sent, returned, and branched. Pair that with TamperCheck's structured verdict for audits and dispute resolution.
Code when you need it — use JavaScript or Python in Code nodes to shape payloads, enrich cases, or gate expensive checks behind rules.
Self-hosted option — run n8n on your infrastructure for air-gapped or strict data policies; TamperCheck still processes files ephemerally per our API contract.
How it works
File in, verdict out — in four steps
Start from a trigger
Use a webhook, schedule, form submission, email trigger, or any n8n node that produces a file URL or bytes — whatever kicks off your document pipeline.
Call TamperCheck
Add an HTTP Request node (or wrap our REST API in a sub-workflow). Authenticate with your TamperCheck API key and POST the document for analysis.
Branch on the verdict
Route automations by verdict, risk score, or finding type — e.g. auto-approve low risk, send medium risk to a human queue, block or escalate tampered files.
Push outcomes everywhere
Write results to Sheets, databases, ticketing systems, or messaging apps. Include the full report URL so reviewers can open the forensic breakdown in one click.
What you see
A verdict card your whole team can read
TamperCheck
APP · just now
Verdict
⚠ Tampered · Risk 72/100
Font inconsistency in totals row (confidence: 0.89)
Running balance mismatch on rows 4–7 (confidence: 0.71)
statement_march.pdf · bank_statement · 2.8s
View full report →- Verdict and risk score — returned as JSON for easy mapping to n8n fields
- Findings list — iterate with Split Out or loop nodes for notifications
- Document metadata — type, filename, processing time
- Report URL — pass through to Slack, email, or ticket bodies
- Raw API response — store in execution data for replay and debugging
Workflows
How teams use TamperCheck in n8n
Loan operations: Ingest applicant uploads from a portal; n8n sends each file to TamperCheck before underwriting systems see the case.
Claims: Attachments from FNOL emails flow through n8n; tampered evidence is flagged before adjusters spend time on the file.
Vendor onboarding: Collect certificates and financials; only documents that pass forensic checks advance to contract signing.
HR: Offer-letter and credential workflows gate on TamperCheck verdicts before HRIS updates.
Security / SOAR: Incident attachments are analysed automatically and enrichment tickets are opened only when needed.
FAQ
Common questions
Be the first to use TamperCheck in n8n
Join the waitlist and we'll notify you the moment the integration is live. In the meantime, start with the API — $5 free credits, no card required.