Example package
Self-host setup
n8n installed on your server or cloud account with backups and updates covered.
You get
- Docker install with HTTPS
- Database and backups
- Update and restore notes
- Admin handover
Sound familiar?
What we hear from businesses before a project like this starts.
- Our Zapier or Make bill grows every month as task counts go up.
- We self-host n8n but nobody knows how it's backed up or updated.
- Workflows fail silently and we find out from a customer.
- We need an integration n8n doesn't have a node for.
- One person built everything in n8n and the rest of the team can't follow it.
What buyers usually need
The requests that come up most often for this kind of work, and what each one takes to work properly.
01
A stable self-hosted install
n8n in Docker with a database, HTTPS, backups and an update routine, or n8n Cloud if that suits you better.
02
Error handling
An error workflow that alerts the right person with what failed and why, plus retries where safe.
03
Migration from Zapier or Make
Existing Zaps and scenarios rebuilt in n8n, run side by side, then switched over.
04
Custom nodes and code
HTTP and code nodes, or a custom node, for APIs n8n doesn't cover.
05
Readable workflows
Named nodes, sticky notes and a short guide per workflow.
Tools that come up most: n8n (self-hosted and Cloud), Docker, PostgreSQL, Caddy or nginx, webhooks, REST and GraphQL APIs, OpenAI and Claude nodes, Google Workspace and Slack.
What you get
Concrete pieces, each one something you can open and check when it's done.
Self-hosted n8n
Docker, database, HTTPS, backups and queue mode where volume needs it.
Docker Compose, PostgreSQLBusiness workflows
Lead routing, order sync, document processing and reporting.
n8n workflowsError and monitoring
Error workflows, alerts and an execution log you can search.
Error trigger, Slack or email alertsZapier or Make migration
Each automation rebuilt, tested side by side and switched over.
Inventory, parallel runCustom integrations
APIs without a built-in node, wrapped so others can reuse them.
HTTP node, custom nodeTypical projects
Example packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
Migrate from Zapier or Make
Your existing automations moved to n8n and run side by side before switching.
You get
- Inventory of current automations
- Rebuilt workflows
- Side-by-side test log
- Switch-over checklist
Example package
Workflow build
A new workflow for one process, with error handling.
You get
- Workflow agreed in writing
- Error alerts and retries
- Test log
- Guide for your team
How we approach it
The habits that keep this kind of project from going wrong.
1
Inventory before migrating
We list every trigger, step and credential before moving anything.
2
Failures are loud
Every production workflow gets an error path that tells a person.
3
Your server, your credentials
Credentials stay in your n8n instance; we work through an account you can remove.
How we work
You describe it. We write it down, build it, and hand it over.
You describe it
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
A written scope
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
Milestones you review
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
Handover and a 30-day fix window
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
What shapes the scope
- Self-hosted or Cloud
- Number of workflows and how complex they are
- APIs without built-in nodes
- Volume and queue needs
Always included
- A written scope before work starts
- Milestones you review and sign off
- Documentation and a walkthrough at handover
- A 30-day window for fixes, at no charge
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See products we've built.
Questions people ask first
Self-hosted or n8n Cloud?
Self-hosting is cheaper at volume and keeps data on your server; Cloud means no server to maintain. We recommend one in the scope based on your volume and team.
Is n8n's license a problem for us?
For internal business use it generally isn't. If you plan to resell or embed n8n, we point out what its license says before you commit.
Will our automations stop during migration?
No. New workflows run alongside the old ones until the test log matches, then we switch.
What happens after handover?
For 30 days we fix anything we built that doesn't work as scoped, at no charge.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com