Skip to main content

n8n Workflow Automation

Zapier, Make (Integromat), Power Automate... these automation services make life easier, but your data transits through American servers, and execution limits quickly drive up the bill. Bunker hosts n8n, an open source workflow automation platform with no limits.

Why n8n?

n8n is a low-code workflow automation platform. Drag-and-drop visual interface, 400+ native integrations, and an execution engine that runs on your infrastructure.

What sets it apart:

  • 400+ integrations: CRM, databases, emails, Slack, REST API, webhooks, and much more
  • Visual interface: build your workflows by drag and drop, no coding required
  • Code when needed: insert JavaScript or Python in any node
  • No execution limits: your workflows run as much as needed
  • Webhooks: real-time triggering via HTTP
  • Self-hostable: your data stays with you

Comparison with Alternatives

CriteriaBunkerZapierMake (Integromat)Power AutomateTemporal
Open sourceYes (Fair-code)NoNoNoYes (MIT)
Sovereign hostingYes (Europe)No (USA)No (USA)No (USA)Depends on you
Execution limitsNone100-50k/month1k-10k ops/monthVariableNone
Visual interfaceYesYesYesYesNo (code)
Custom codeYes (JS/Python)LimitedLimitedLimitedYes
400+ integrationsYesYes (7000+)Yes (1500+)Yes (1000+)No (SDK)
Real-time webhooksYesYesYesYesYes
High availabilityGuaranteed (Queue mode)YesYesYesYour responsibility
Ops costZero$19-$599+/month$9-$299+/month$15+/monthTime + server

What Really Changes

No execution limits. With Zapier, the Pro plan at 750 tasks/month costs $19.99/month. At 50,000 tasks, it's $599/month. With n8n hosted by Bunker, your workflows run without a meter.

Your data stays in Europe. Workflows often handle sensitive data: customer contacts, financial data, API tokens. With n8n on Bunker, nothing leaves the territory.

The source code is auditable. Fair-code license: you can inspect exactly how your data is processed.

You Keep Control

  • JSON export: export all your workflows in one click
  • REST API: manage your workflows, executions and credentials via API
  • Migration: reimport your workflows on any n8n instance
  • Community: 400+ workflow templates shared by the community

Why Bunker Instead of Self-Hosting?

You could install n8n on your own server. But:

AspectSelf-hostingBunker
High Availability modeTo configure (workers + Redis + PostgreSQL)Included (Queue mode)
Parallel workersTo sizeConcurrency 10, pre-configured
DatabasePostgreSQL to manageCNPG PostgreSQL (2 replicas)
Message queueRedis to deployRedis replication included
EncryptionN8N_ENCRYPTION_KEY to generateGenerated and secured
StorageTo provision20 Gi ceph-rbd included
BackupsTo configureAutomatic
Security updatesTo monitorApplied
24/7 monitoringTo set upIncluded

In Queue mode, n8n separates workflow editing from execution. Workers process tasks in parallel (concurrency 10), ensuring your workflows execute even under heavy load.

Quick Start

1. Deploy from the Console

  1. Go to console.getbunker.net
  2. Create your account or log in
  3. Deploy n8n from the service catalog
  4. Wait a few minutes for the instance to be ready

2. Create a First Workflow

  1. Open the n8n visual editor
  2. Click "+" to add a trigger node (Webhook, Schedule, etc.)
  3. Add action nodes (send email, call API, write to database)
  4. Connect nodes by drag and drop
  5. Test with "Execute Workflow"
  6. Activate the workflow

3. Configure a Webhook

Webhooks let you trigger a workflow via HTTP:

  1. Add a "Webhook" node as trigger
  2. Configure the method (GET, POST) and path
  3. n8n generates a unique URL
  4. Send an HTTP request to this URL to trigger the workflow
# Example: trigger a workflow via webhook
curl -X POST https://your-instance.getbunker.net/webhook/my-workflow \
-H "Content-Type: application/json" \
-d '{"event": "new_order", "order_id": 12345}'

Advanced Features

Queue Mode (High Availability)

Queue mode separates components for reliable execution:

  • Main: manages the interface, webhooks, and sends tasks
  • Workers: execute workflows in parallel (concurrency 10)
  • PostgreSQL: stores workflows and execution history (CNPG, 2 replicas)
  • Redis: message queue between main and workers

REST API

Manage everything via API:

# List workflows
curl https://your-instance.getbunker.net/api/v1/workflows \
-H "X-N8N-API-KEY: YOUR_KEY"

# Activate a workflow
curl -X PATCH https://your-instance.getbunker.net/api/v1/workflows/123 \
-H "X-N8N-API-KEY: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"active": true}'

Scheduled Executions

Schedule recurring workflows:

  • Data synchronization every hour
  • Daily report sent by email
  • Weekly database cleanup
  • Monthly token renewal

Best Practices

  • Use n8n credentials to store your API tokens (encrypted with N8N_ENCRYPTION_KEY)
  • Enable error notifications to be alerted if a workflow fails
  • Regularly export your workflows as JSON (or use the API)
  • Use sub-workflows to factorize common logic
  • Test your workflows in manual mode before activating them

Next Steps