Secure Your Cloudflare KV n8n Workflows
Harden Cloudflare KV workflows in n8n: credentials, signatures, PII handling, and audit logging.
Key takeaways
- Credentials belong in the vault, nowhere else.
- Verify every webhook signature.
- Mask PII in logs.
- Audit every write.
Cloudflare KV workflows touch sensitive data. This guide covers credentials, signature verification, PII handling, and the audit log you'll wish you had after your first incident.
Credentials
Store Cloudflare KV credentials in n8n's credential vault only. Never in workflow JSON, sticky notes, or env vars readable by every workflow.
Signature verification
Every inbound webhook from Cloudflare KV must be signature-verified. Reject unsigned with 401.
PII handling
Mask emails and phone numbers in logs. Never log full payloads if they contain Cloudflare KV PII — hash or truncate.
Audit
Persist a compact audit log for every write to Cloudflare KV: workflow, actor, timestamp, record ID, before/after. You'll need it.
Frequently asked questions
- Does n8n encrypt credentials?
- Yes, with an encryption key you control. Rotate it periodically.
- SOC 2 / ISO 27001?
- Yes for n8n Cloud. Self-hosted, you inherit the compliance of your infra.
- How do I handle GDPR deletes?
- Have a workflow that erases Cloudflare KV PII across all downstream systems on request.
- Who should see prod credentials?
- As few humans as possible. Prefer service accounts and short-lived tokens.