21 automations moved from Make to self-hosted n8n
The agency moved from a pay-per-operation plan to its own server with unlimited runs, with security, backups and more reliable workflows.
- Client
- Agência DPR
- Type
- Automation & AI
- Year
- 2026
- Stack
- n8nDockerPostgreSQLRedisGoogle SheetsSlackNotion
Built for DPR agency projects
The challenge
21 Make scenarios, billed per operation, adding up to thousands of runs a month and getting pricier with every new client.
What I built
Infrastructure before code: a self-hosted n8n in queue mode, with database, cache, TLS, backup routine and hardening. Then the workflows were migrated one by function, standardized and documented.
Highlights
- →Own server with queue, database and TLS, with backup and restore
- →Workflows generated from config, one per client
- →Fixes the old flows missed (click source, refunds)
- →Automatic Slack alerts when something fails
How it works
Lead capture
- 1Formulário
the lead fills in the form
- 2Webhook
n8n receives it instantly
- 3Normaliza
fixes mismatched fields and formats
- 4Planilha / banco
the client's master base, always organized
Sales into the database
- 1Checkout
a sale happens
- 2Webhook + assinatura
n8n checks the event is legitimate
- 3Supabase
sale, order and refund in the right places
- 4Conciliação
every hour, cross-checks with the API
Notion → Slack
- 1Menção no Notion
someone gets tagged in a comment
- 2n8n
finds that person in Slack
- 3DM no Slack
the notice reaches them where they are
Want something like this for your business?
Message me on WhatsApp