Over the past year, a collection of individually built automations has quietly turned into something closer to a connected internal system. This is a rundown of what the current stack looks like and how the pieces fit together.
The core pieces
n8n as the connector.
Most workflows run through n8n, which sits between our other tools and moves information between them without needing custom integrations for each one.
Slack as the alert layer.
Rather than emails that get buried, anything time-sensitive, renewal reminders, uptime alerts, stalled project flags, lands in a dedicated Slack channel the team actually watches.
A central project database.
Client, project, and renewal information lives in one place rather than scattered across separate spreadsheets and platform dashboards, and most workflows read from or write to this same source.
How a single event flows through the system
Take a new client signing on as an example. A new record is created in the project database, which triggers an n8n workflow that sets up the relevant Slack channel, creates a starter project checklist, and adds the client’s domain and hosting details, if known, into the renewal tracker automatically.
What this replaced
Before this stack existed, each of these steps was a manual checklist item, easy to forget under a busy week, and inconsistent depending on who was onboarding the client. Now the baseline setup happens the same way every time, regardless of who is doing it.
What we are careful about
Automations that touch client-facing systems, like actual site changes or billing, still go through a manual review step rather than running unsupervised. The stack is built to remove repetitive internal admin, not to make irreversible decisions without a person checking first.
What is next
The current gap is reporting: pulling status from across the stack into a single weekly internal summary, rather than each piece being useful individually but not yet talking to each other for a combined view.