Choosing n8n: Cloud, self-hosting and a nightly process

Define the business result of the nightly job

Consider matching an order API with dispatch records nightly and giving the operator a list awaiting dispatch. Running at one in the morning does not define whether the data covers yesterday or everything since the last completed window. Specify time zone, order identity, cancellations and late records. Begin with a comparison list rather than changing live dispatch state. Match it with the existing manual report. The adoption condition is an explainable unfinished-order list, not merely a green execution indicator after one scheduled run.

Translate execution pricing into this design

Cloud pricing centers on monthly workflow executions rather than counting every ordinary step individually. Execution boundaries still depend on the design: one daily retrieval differs from a trigger for every order. Sufficient monthly allowance also does not prove sufficient concurrency, runtime or retained investigation history. Evaluate normal days and month end with pagination and slow API responses included. A longer diagram does not automatically establish a cost advantage over another meter. Price the actual way the process starts and completes, with external-service bills kept separate.

Keep the Cloud offer and maintenance budget distinct

The verified Starter configuration provides 2,500 executions for EUR 20 monthly equivalent annually, a EUR 240 annual base, or EUR 24 month to month. This is not a total including tax, separately contracted APIs or AI usage. Cloud does not remove responsibility for changed order fields or expired app authorization. Include a person who reviews the morning result and a route for requesting corrections. Choose the annual commitment after establishing that capacity and administrative requirements remain useful throughout it, rather than treating the displayed equivalent as a monthly cancellable bill.

Self-hosting includes restoring usable credentials

A Community installation requires assigned owners for servers, upgrades, storage, monitoring and backups. n8n encrypts credentials using an encryption key, so saving only a database should not be treated as a complete recovery plan. Retain the key securely and rehearse restoration until connections are usable in an isolated environment. Prevent that restored environment from dispatching or notifying alongside production. A software entitlement without a subscription does not supply the people or infrastructure required to meet a daily deadline. Include absence cover when evaluating the operating arrangement.

Match permissions and license scope to the actual use

Self-hosting does not imply that every sharing or administrative capability is included in Community. Official workflow-sharing guidance distinguishes Cloud entitlements from self-hosted ones. Separate builders, result reviewers and connection administrators before selecting an edition. The Community FAQ also distinguishes workflows maintained inside your organization from offering editing capabilities to outside users. If customers will edit workflows within a product you sell, verify the required agreement with n8n. Do not convert deployment control into a general permission claim about every commercial architecture.

Distinguish an empty day from incomplete retrieval

A truly empty day differs from zero results caused by an expired connection or wrong selection. Do not require every day to match yesterday; expose the requested window, pages, exclusions and unfinished work instead. Rehearse a second-page failure, repeated processing of a window and a late order after the report was produced. Establish destination checks before repeating dispatch changes or messages. Ask an operator other than the builder to explain the discrepancy and correction route. This proposed evaluation supplies a practical continuity criterion without inventing a product reliability measurement.

Treat exported logic as one part of the move

Official JSON export preserves workflow logic, but inspect credential names, IDs and any authentication headers introduced through cURL before sharing a file. Export alone does not migrate credentials, history or records in outside services. Preserve the last completed business window and compare equivalent inputs at the destination. Moving to self-hosting and ending a Cloud subscription are separate tasks. Retain required records, agree when the old writer stops and the replacement starts, and check applicable subscription timing before cancellation. A saved workflow is useful migration material, not proof of a completed operational move.

• n8n pricing: Starter, Pro and a self-hosting budget
• Choose scheduled API jobs by completeness and recovery