How do you start an n8n workflow without an app connection?

Use a Manual Trigger and an Edit Fields node to make one fake signup. A node is a step in the workflow. This starting example gives you an output to inspect before connecting an account or database.

Draw a manual start
On paper, draw the first node and label it Manual Trigger. It runs when you choose to start the workflow.
Add the signup fields
Draw an Edit Fields node and give it an ID of demo-103 and a made-up interest. Write out the two values you expect the node to pass on.
Choose where a real save would go
Add a pretend destination and draw the repeated input. Keep one saved row per ID at the destination. The manual example can stop at the output.

What should you check before retrying an n8n execution?

Open the failed execution and check its input and last confirmed result. A retry keeps the results of completed steps. The failed step can process all its saved input again, including items it already handled.

Suppose one step sends two messages and fails after sending the first. A retry of that step can send the first message again. A failed step that calls another workflow can also rerun that workflow from its start. Check the destination before retrying. For a saved record, use a unique ID at the destination so an already-saved record can be found or updated.

While the failed run is stored, you can retry with the original workflow or the one you have since saved. Edits in the saved workflow apply to steps that have yet to finish. The Remove Duplicates node can compare values within one input or across runs. Keep any necessary record of completed actions in the destination app because execution history can be pruned.

When can a person review an n8n agent action?

You can attach human review to a specific tool an AI agent might call. The workflow pauses for a reviewer to see the tool and proposed inputs. Denying the request cancels that action.

Keep this separate from ordinary signup copying. If an agent suggests an outgoing message, review the recipient and text first. Confirm what happens on denial or no decision in a disposable setup before giving it write access.

How do n8n Cloud and self-hosting affect costs?

n8n Cloud charges by workflow execution. One execution is a run of the whole workflow. The hosted Starter display in November 2026 listed €20 per month billed annually, 2,500 monthly executions and up to five at once.

With a self-hosted setup, someone has to run the server, update it and protect and restore its data. n8n makes Community source available under its Sustainable Use License, with internal business and personal-use scope. Check the license if customers will use the workflow editor or connect their own accounts through your product.

Connected apps can have their own bills, and included assistant credits are a separate allowance.

What should you keep when moving n8n?

Export the workflow JSON and list its connected accounts and dependencies. Recreate credentials at the new destination and review the export before sharing it, since it can contain credential names or sensitive values set on a request.

Back up any stored data separately. If you run your own n8n instance, securely keep the encryption key needed to read credentials in a restored database. Restore a private copy and check that it can handle one fake event. Plan the switchover so only one copy receives new events.