Sample report
Example n8n Workflow Audit Report
This is a fixed, sanitized sample built from the Auturance Risky Lead Intake Demo. It shows the shape of a report without using a real customer workflow, customer data or a live scan.
Workflow overview
The sample path is a fixed demo: webhook → AI lead classifier → CRM contact → sales notification. It contains no credentials and is not a real customer workflow.
Static score
This is a deterministic static review score, not a runtime pass/fail result.
Top production risks
High · reliability
External side effects have no visible failure handling
The sample path writes to external systems but does not show a connected workflow-level recovery path.
High · AI validation
AI output may reach a side effect without strong validation
The AI-generated lead fields can reach Create HubSpot Contact without an explicit validation boundary.
Medium · idempotency
Create/append operations may duplicate business data
A repeated webhook or retry can create the same CRM contact again when no duplicate-prevention signal is visible.
Example reliability finding
WL008External side effects have no visible failure handling
Static evidence points to a reliability question: what should happen when the CRM write or sales notification fails after an earlier step has already completed?
Example security finding
WS004Unauthenticated webhook may reach an external side effect
The sample export does not show an explicit n8n authentication mode before the webhook reaches a detected business write. An upstream gateway may still exist, so this remains a static signal to verify.
Example AI validation finding
WL004AI output may reach a side effect without strong validation
The AI-generated lead fields can reach Create HubSpot Contact without an explicit validation boundary.
Coverage transparency
- The graph contains four nodes and three main connections, with one webhook trigger and one AI node.
- The report separates reliability findings from security findings instead of folding them into one score.
- Coverage describes what the static map recognized; it does not claim that every n8n or external-system behavior is understood.
- The sample contains no credential values and is not connected to a customer account or runtime environment.
Production checklist
- Validate the AI response before creating a CRM contact.
- Define duplicate-prevention or idempotency behavior for repeated leads.
- Add and test an error path for the CRM write and notification.
- Confirm webhook authentication and any upstream signature control.
What the report does not prove
- The report does not execute the workflow or verify that HubSpot, Slack or the webhook is reachable.
- The score does not prove that the lead mapping, credentials, AI response or business outcome is correct.
- The sample report is an explanation of static evidence, not a runtime test result.
See what your workflow reveals
The sample is intentionally limited. Upload your own authorized n8n export to receive a report shaped by its actual graph and visible signals.