n8n
n8n: a first setup, important settings, verification, and recovery considerations.
Working directory: ~/homelab/apps/automation. Follow the common setup workflow first. This is a setup note based on the linked documentation, not a copy of my live configuration or a runtime verification of this full stack.
Start here
n8n connects triggers to actions. Begin with its Docker setup and a manual workflow that transforms fixed text. Do not connect email, banking, production webhooks, or destructive actions during your first test. A PostgreSQL deployment adds a separate database service and its backup procedure.
Settings and data
Persist /home/node/.n8n even when using PostgreSQL. Keep N8N_ENCRYPTION_KEY stable and backed up with the database; replacing it can make saved credentials unreadable. Set timezone deliberately. Configure the external editor/webhook URLs only after deciding how access will work.
Check it
Run the manual workflow, inspect each node's input and output, then restart and run it again. A successful manual run does not prove that a schedule or webhook works. Test those separately with disposable data and the expected timezone.
When something fails
For database errors, verify service names, credentials, readiness, and database logs. For webhook failures, distinguish test and production URLs and check workflow activation. Limit execution-history retention: inputs and outputs can contain secrets. Restore the database, configuration, and encryption key together.