The automation spine behind Kratt operations.
One-off automations rot when they live on random laptops, undocumented cron jobs and personal tokens. Kratt needed a shared automation base that could run lead, content, CRM and reporting loops without exposing admin surfaces.
How these were measured: Source: operations/systems/K-02-n8n-shared-instance.md records the runtime, workflow count, active count, retention and operating notes.
What we shipped
We run a shared n8n instance with Postgres state, a public webhook front door, private admin access and execution retention. On the 2026-08-17 system card it held 21 workflows, 14 active, across Kratt outreach and operations.
What this page does not claim
- No secrets, credentials, host addresses, public webhook paths or private admin URLs are exposed.
- No claim that every workflow is healthy or revenue-producing. The source card says what exists and what was active, not what it earned.
- No client data, recipient data or message copy is published from any workflow.
Where is your business leaking revenue?
A free AI audit finds it, ranked by impact, and it is yours to keep.
Back to all case studies, or see every live build on the portfolio wall.