Appearance
n8n
n8n handles the automations: connecting webhooks, schedules and APIs without writing a whole service.
- Runs as a Coolify service in
platform: n8n, its own Postgres, and n8n's task runners. - UI at
n8n.stu-bot.uk, behind Cloudflare Access, then n8n's own login. - Webhook paths (
/webhook/...,/webhook-test/...) bypass Access, so outside services can call them. Every webhook workflow has to check a secret, using n8n's header auth or by verifying a signature. - It's joined to the
coolifynetwork, so workflows can reach the bus and the Claude runner by name. - Its Postgres is backed up daily to R2 like every other database.
Talking to the rest of the stack
- Onto the bus: an HTTP Request node to a small internal endpoint, or Redis nodes that add to a stream.
- To Claude: an HTTP Request node to
http://claude-runner:8080/jobswith the runner's bearer token (stored as an n8n credential). See Claude on the server.
Planned inputs
- Email: Cloudflare Email Routing → an Email Worker → an n8n webhook →
email.inboundon the bus. - SMS: an old Android phone running SMS Gateway for Android → an n8n webhook →
sms.inbound.