Automatisch

Last reviewed Aug 26, 2026 · 897 words

Automatisch is the one to pick if the people building the automations are not developers. Its flow editor is a deliberate copy of Zapier's shape: one trigger, a vertical list of steps, each step a form. n8n is a node graph with expressions and code blocks, more capable and less approachable. If you have watched a colleague give up on n8n after 20 minutes, Automatisch is the tool that colleague will finish a flow in. The price is a smaller connector catalogue and a project still filling out the features Zapier has had for a decade.

It copies Zapier on purpose, and that is the pitch

A flow is a trigger followed by actions. Pick "New row in a Google Sheet", add "Send a message in Slack", map fields by clicking on values from the previous step's test output, turn it on. There is no canvas, no wiring, no expression language to learn beyond picking variables from a list. Multi-user with roles is included, and every credential you connect stays in your Postgres database encrypted with a key you set, which is the reason to run it at all: an automation tool sees the contents of every system it touches, and a hosted one sees them on someone else's servers. The AGPL-3.0 licence means the whole product is open, with a hosted plan from the developers if you would rather pay than operate. It launched in 2022, has 13,900 stars, and moves quickly.

The stack is Postgres, Redis, and two copies of the app

services:
  main:
    image: automatischio/automatisch:latest
    ports:
      - "3000:3000"
    environment:
      HOST: automatisch.example.com
      PROTOCOL: https
      PORT: 3000
      APP_ENV: production
      APP_SECRET_KEY: change-me-64-random-chars
      ENCRYPTION_KEY: change-me-64-random-chars
      WEBHOOK_SECRET_KEY: change-me-64-random-chars
      POSTGRES_HOST: postgres
      POSTGRES_DATABASE: automatisch
      POSTGRES_USERNAME: automatisch
      POSTGRES_PASSWORD: strong-password
      REDIS_HOST: redis
    depends_on: [postgres, redis]
  worker:
    image: automatischio/automatisch:latest
    environment:
      WORKER: "true"
      # same variables as main
    depends_on: [postgres, redis]
  postgres:
    image: postgres:16
  redis:
    image: redis:7

The main container serves the UI and API; worker executes flows from a Redis queue, and you can run several. HOST and PROTOCOL must match the public URL or webhook addresses generate wrong, which is the same mistake as every other webhook-driven tool. The three secret keys are used to encrypt stored credentials; generate them once with openssl rand -hex 32, keep them with your backups, and understand that losing ENCRYPTION_KEY means every connected account has to be re-authorised. The default login on a fresh install is [email protected] with password sample; change it before the container is reachable by anyone else. Memory sits around the catalogue's 512 MB for a light install, more with busy workers.

The connector count is the honest limit

Zapier lists thousands of apps. Automatisch's catalogue is measured in dozens, weighted towards the ones self-hosters and small teams actually use: Slack, Discord, Telegram, GitHub, GitLab, Notion, Google Sheets, Airtable, Mattermost, Stripe, various forms tools, plus generic HTTP, RSS, scheduler and webhook triggers. Before committing, list the 5 systems you need to connect and check each one on the integrations page. If two are missing, the escape hatch is the HTTP action combined with the incoming Webhook trigger, which together cover any service with an API at the cost of reading its documentation yourself. What you cannot easily do is write a custom step in JavaScript inside the flow, which is the point where n8n or Activepieces start to pull away.

Webhooks do most of the real work anyway

In practice, the flows that survive in a homelab are boring: a webhook from Uptime Kuma posts to a chat room; a form submission becomes a row in a sheet and a Telegram message; a new release on a GitHub repo triggers an HTTP call to a deploy hook. Those need three connectors, and Automatisch has them. The ones that suffer are the deep integrations, syncing two CRMs field by field, where Zapier's decade of edge-case handling shows. Keep expectations at "glue between systems" rather than "integration platform" and it delivers.

Pick by who is building, not by feature list

If you are the only user and you can write a little JavaScript, n8n's ceiling is far higher and its self-hosted licence is fine for personal use. If a team of non-developers will build and maintain flows, Automatisch is the tool they will not abandon. If you want something in between, with a marketplace of community pieces and a friendlier editor than n8n, look at Activepieces. For event-driven hardware and home automation glue, Node-RED remains the better fit. The automation category lists them side by side, and the Zapier alternatives page frames the switch from the paid service.

What I'd do

Automatisch for the office or the family: Postgres 16 and Redis in the same compose file, one worker to start, HOST set to the real domain behind a reverse proxy, the three keys generated with openssl and copied into the password manager, default account replaced on the first login. Nightly pg_dump. For my own homelab glue I would still reach for n8n, but that is because I am the developer in this scenario, and this tool was not built for me.