n8n Review: Workflow Control, Hosting and Running Costs

n8n is a workflow platform to consider when your team needs to own the logic between an event and its outcome. The useful question is not whether it can connect two services. It is whether a colleague can understand, repair and safely rerun the process when one of those services stops behaving as expected.

Who should shortlist it

A technical operations team with a named maintainer is a stronger fit than a team looking for a maintenance-free assistant. The official hosting documentation offers both managed cloud and self-hosted options, with different editions. Self-hosting moves infrastructure work to your team; it does not remove the cost of running the process.

Before choosing an edition, list the required connectors, credentials, collaboration controls and execution visibility. Check those against the actual plan. Treat feature access and the right to use the software for your intended business model as separate checks; do not assume every self-hosted use is unrestricted merely because source is available.

A useful first workflow

Build a reviewed sales-call handoff: accept a fictional call summary, extract proposed next actions, validate required fields, and create a draft for the account owner. Keep the CRM write disabled at first. The worked handoff includes a conditional promise that must not become a confirmed deadline.

Execution record to keep
source_record_id, source_version, workflow_version
review_status, destination_record_id, attempt_number
failure_stage, recovered_at

The record is your design, not a claim that every field appears automatically in n8n. Its purpose is to make the process recoverable. If a CRM write succeeds but the next notification fails, a retry must not create a second CRM activity. Use the source identity to find the previous result before repeating a write.

Cloud versus self-hosting

Cloud reduces infrastructure ownership but still leaves you responsible for workflow behavior and credentials. Self-hosting adds updates, backups, restoration tests and monitoring. Include the time of the person on call in the comparison. A free software edition running on a neglected server can cost more than a paid service when a business process stalls.

Compare with Make and native integrations

Make is a useful comparison for a team that wants to inspect a visual scenario and its individual run outputs. A native CRM integration may be preferable if it already implements the exact handoff with adequate error reporting. Use our same-workflow comparison to compare ownership and recovery rather than counting connectors.

Purchase only after a representative workflow passes a normal run, a duplicate event and a partial-failure recovery. Check current execution allowances, retention and external AI usage separately. We have not run a performance or reliability benchmark for this assessment.