What does n8n automation cost to implement and run?
The n8n subscription is only one part of the cost. A business workflow also needs implementation, access to connected systems, testing and someone responsible for keeping it working. Compare those separately before choosing a provider.
Separate four cost categories.
- Implementation
- Mapping the existing task, configuring connections, building the workflow, testing exceptions and preparing handover documentation. Agree what is delivered before comparing setup fees.
- Platform or hosting
- A managed platform subscription or the infrastructure and administration needed for self-hosting. Ownership and operating responsibility should be explicit.
- Connected tools and usage
- CRM, messaging, email or model-provider charges where applicable. Ask which accounts you need and how usage is limited or billed.
- Maintenance
- Monitoring arrangements, expired access, changed APIs, workflow changes and support. Clarify which fixes are included and which need a new quote.
There is no single published Media87 price for every n8n project. Send the workflow and systems you need connected so we can confirm feasibility, responsibilities and a scoped quote.
n8n lists execution-based pricing and hosted or self-hosted options on its official pricing page. Check current plan limits there; this guide is not a copy of its rate card. Platform fees are different from Media87’s implementation work.
What makes one implementation more involved than another?
Count the decisions, exceptions and responsibilities, not just the nodes in a diagram. The following are illustrative scopes, not completed client projects or priced packages.
- Form → assigned enquiry
- Map required fields, duplicates, destination and the receiving person. Test missing fields and a destination that cannot accept the record.
- Email → reviewed draft
- Add classification rules, approved knowledge, uncertain-message handling and a person who approves the reply. Agree what must never be sent automatically.
- CRM → connected follow-up
- Check custom fields, matching records, permission levels and the effect of retries. A failed update must not create duplicate records or trigger repeated customer messages.
Ask whether existing connectors support your account and the required action. Custom API work, undocumented systems or unclear business rules can change the scope. A standard CRM rule may be enough; you do not need AI in every workflow.
Managed hosting or self-hosting: who owns operations?
Discuss who owns the account, credentials and workflow export. If you choose self-hosting, include server administration, updates, backups, access controls and recovery responsibilities in the comparison. Self-hosting is an operating choice, not a promise of zero cost.
Decide what execution information may be retained and who can view it. Keep unnecessary personal information out of logs and reports. Your proposal should identify the agreed operating arrangement rather than implying an unverified security certification.
Compare first-year costs using your own figures.
Compare the figures in your own quote.
Enter amounts in one currency. This worksheet adds your figures; it does not estimate Media87 fees, vendor prices or exchange rates. Do not include the same cost twice.
First-year total = one-time implementation + 12 × monthly costs. Tax, overages and later changes are excluded unless you include them. Blank fields count as zero; complete all fields for a full comparison.
Your figures stay in this page’s memory; this worksheet does not send or save them. With JavaScript disabled, use the formula above.
What should the implementation quote actually deliver?
- A workflow boundary: trigger, inputs, decisions, destination and excluded cases.
- A test sheet: expected results for success, duplicates, missing data, expired credentials and unavailable systems.
- An approval path: where a person checks a draft, uncertain decision or customer-facing action.
- Handover: the agreed workflow export, operating notes, access ownership and manual fallback.
- A change policy: how new fields, integrations or business rules are requested and priced.
Agree a controlled release and a way to pause the workflow. A successful demonstration with one sample is not enough to establish reliable operation.
Send a brief that can become a quote.
Describe the task as it works today, the tools involved, approximate activity volume, destination, approval owner and what happens when a step fails. Share redacted examples, not passwords or private customer records.
