Projelere Dön

Production N8n Workflows

Production-ready n8n workflows for self-hosters and small teams

Proje türü
Open Source
Dil
JavaScript
Yıldız
0
Fork
0

Production n8n workflows connecting security, monitoring, backups, GitHub, domains, and alerts

Production n8n Workflows

Small, auditable automations for self-hosters and small teams.
Safe first runs, bounded retries, clear setup guides, and no exported credentials.

Validate workflows n8n 2.41.4 MIT License Latest release

Why this collection exists

Most workflow collections optimize for volume. This one optimizes for trust: every workflow is intentionally small, documents its failure behavior, keeps secrets out of exported JSON, and can be reviewed before it is activated.

Workflow catalog

WorkflowOutcomeSetupServicesImport
Service health monitorDetects unhealthy Dockerized services through HTTP health endpoints5 minHTTP, Discord-compatible webhookJSON
Domain and TLS monitorChecks registration expiry and verifies that HTTPS/TLS works5 minRDAP, HTTPS, webhookJSON
PostgreSQL backup verifierRequires fresh size, checksum, and restore-test evidence10 minBackup job, webhookJSON
GitHub release watcherAlerts once when a tracked project publishes a release5 minGitHub API, webhookJSON
Human-reviewed AI ticket triageProduces a classified draft and stops at a review queue10 minOpenAI-compatible API, webhookJSON
CVE security digestSends one daily digest of newly published high-severity CVEs5 minNVD, webhookJSON
Domain expiry monitorWarns before domain registration expires5 minRDAP, webhookJSON
GitHub issue triageApplies deterministic labels to new issues10 minGitHub webhook and APIJSON
Backup failure alertNormalizes backup events and alerts only on failure5 minAny backup tool, webhookJSON
Website change monitorKeeps a private baseline and alerts when page text changes5 minPublic website, webhookJSON

Quick start

  1. Open a workflow's JSON link in the table and save the file.
  2. In n8n, choose Workflows → Import from File.
  3. Open the visible Config node and replace every placeholder.
  4. Connect credentials when the guide asks for them. Credentials are never included in exports.
  5. Execute manually once and inspect every output.
  6. Activate only after the test run succeeds.

What “production-ready” means here

  • No credential exports. Authentication is connected after import.
  • Safe first run. Stateful monitors establish a baseline instead of generating noise.
  • One visible Config node. Important values are not scattered across the canvas.
  • Failure-aware. Network calls use retries and bounded timeouts.
  • Human control for AI. The AI workflow only drafts; it never sends a customer reply.
  • Least privilege. The health monitor does not mount or expose the Docker socket.
  • Small enough to audit. This is not a scraped “thousands of workflows” dump.

Local validation

The included Compose file pins the n8n version used for schema validation:

cp .env.example .env
# Replace N8N_ENCRYPTION_KEY before first start.
docker compose up -d

Run the repository validator with:

npm test

It checks JSON syntax, required workflow fields, node and connection integrity, duplicate IDs and names, exported credential references, and common secret formats. GitHub Actions runs the same check on every push and pull request.

Compatibility

Workflow exports use built-in nodes available in n8n 2.x and are maintained against 2.41.4. External APIs can change; every guide documents the expected payload and upstream dependency.

Contributing

Read CONTRIBUTING.md. Production experience, reproducible bug reports, and small improvements are preferred over workflow count.

If one of these workflows saved you time, consider starring the repository. It helps other self-hosters discover a smaller, reviewable alternative to bulk workflow dumps.

License

MIT