n8n
hosomaki.n8n
A Docker Compose file for n8n alone, generated from the catalog and checked by the safety inspector. No account needed.
Workflow automation platform with 400+ service integrations, extensible in JavaScript. Runs event-driven and scheduled flows across APIs, databases and model endpoints.
n8n represents an automation as a directed graph of nodes on a canvas, where each node either triggers a run or performs one step against a service, and data passes between them as JSON items. Triggers cover webhooks, schedules, queue messages and polling checks, and any gap in the integration library is closed with a code node or a generic HTTP request. Credentials are stored once and referenced by nodes rather than embedded in each workflow, so rotating a secret does not mean editing every flow that uses it. A first deployment usually pairs a manual trigger with a single HTTP request node, then adds a schedule once the flow is proven.
You know it worked when
- The workflow canvas loads in the browser.
- A two-node workflow executes and its run appears in the execution history.
- One external service authenticates successfully.
- A scheduled workflow fires without manual intervention at its next interval.
Known sharp edges
- Complex multi-node workflows need memory headroom beyond the default allocation.
- External integrations require their credentials configured before a workflow will run.
- Execution history and stored credentials live in the configured database; with the default embedded store on a non-persistent volume, both are lost when the container is recreated.
- Webhook triggers need the externally reachable URL set explicitly, or registered callbacks point at an address the calling service cannot resolve.