Skip to content
AspirecoStart

Platforms / n8n

n8n automation

Aspireco builds and runs automation on n8n: workflow estates for routing, enrichment, approvals, escalation and digests, self-hosted on infrastructure we control. Our own operating layer runs an estate of 117 workflows across eleven businesses.

What we run on it

  • Business OS — a shared estate of 117 workflows, namespaced per business, so each venture inherits routing, notification and escalation patterns instead of rebuilding them.
  • POD Engine — fourteen production workflows from trend to storefront, with one human approval gate driven through a chat bot.
  • Content Factory — a short-form video pipeline that scripts, sources, voices, renders, publishes and attributes on a schedule.
  • Norpex — five always-on automations behind a marketplace checkout, including a Stripe event router and the escrow cron.

How we build on it

Workflows hold the routing; logic that must be exact lives in code the workflow calls. On Growth Engine, the Next.js app stays the source of truth and n8n runs as a stateless task runner called by webhook. Every run is observable — what ran, what it cost and what it decided — and failures reach a person as a digest.

Self-hosted

We run it on infrastructure we control, as part of the operating stack behind Business OS, with secrets brokered centrally so a credential rotates without redeploying every consumer.

Questions

Can you take over an n8n setup we already have?

Often, yes. The audit maps what each workflow does, which ones hold state or move money, and where failures go unnoticed, then says what to keep, what to consolidate and what belongs in code.

Can you run and monitor n8n for us?

Yes, under retained capacity: infrastructure operation plus monitoring, digests and escalation for the automation estate, sized to what it looks after. Work happens in your own infrastructure accounts wherever possible.

When should logic move out of n8n and into code?

When a step must give the same answer every time — money, compliance, pricing — or when a workflow has started holding the application's state. Those belong in code the workflow calls.