Pricing

An execution is when n8n completes one cycle of the workflow that you’ve built. You can make as many executions as you like in any of our self-hosted plans — regardless of how complex the workflow is or how much data it uses.

Workflows are either 'test' or 'active'. A 'test' workflow is triggered by clicking a button in n8n. This is handy when building workflows as it gives you immediate feedback on whether things are working.

Test workflows can be activated when they’re ready, which allows them to be triggered automatically.

Dedicated support gives you direct access to our in-house support team, with an SLA for response times.

Forum support is offered on the n8n community forum, which consists of over 4,000 tech enthusiasts and professionals plus our community engineers.

Workflows are either 'test' or 'active'. An 'active' workflow can be triggered automatically (e.g. at regular intervals, or when an event happens in another system).

Note that if an active workflow contains multiple triggers, each will count as an active workflow. For example, 1 active workflow with 3 triggers will count as 3 active workflows.

Log streaming allows you to automatically pipe n8n activity to an external log aggregator of your choice (e.g. Datadog, Splunk, syslog), allowing you to deal with them using a similar process to the one you use for other tools.