When you activate the plan, you receive a hosted n8n workspace provisioned in the cloud. You don’t need to install n8n, configure databases, or manage updates just to get started. The plan is designed to be “click-and-go” so you can focus on building workflows.

Included: 200 workflow executions per month, unlimited workflows, and unlimited users. This means you can build as many workflows as you want and collaborate with your team, while execution usage is the main monthly meter.

It’s perfect for learning, prototyping, internal automation, lightweight production use cases, and validating integrations before scaling up.

A workflow execution is counted when a workflow runs from start to finish. For example, if a webhook receives a lead, checks conditions, calls an API, and sends a Slack message, that entire run is one execution.

Executions can increase quickly if you run workflows on frequent schedules or if your webhook endpoints receive many events per day. A smart approach is to filter early (ignore events you don’t need), batch actions where possible, and avoid duplicate workflows triggering on the same event.

If you expect high volume, this plan is still a great starting point—use it to build and test your workflow logic, then upgrade once you confirm your usage pattern.

Yes, for many small and predictable production workloads. If your business automations run a limited number of times per day (for example, scheduled reporting, basic lead routing, notifications, or simple API syncing), this plan can work well.

For mission-critical workflows (payments, order fulfillment, time-sensitive alerts), we recommend adding safeguards: retries for temporary failures, error-handling branches, alerts/notifications, and test workflows to validate changes before going live.

As your business grows, upgrading gives you higher execution limits and more headroom so your automations never become a bottleneck.

No. You can activate the plan without adding payment details. That’s why it’s ideal for trying n8n, building proof-of-concepts, and validating integrations without friction.

When you need higher limits, you can upgrade at that time. Your workflows and workspace remain intact—no rebuilding needed.

n8n supports many integrations out of the box and also works with custom APIs. You can authenticate using API keys, OAuth, or custom headers depending on the service. Typical workflow patterns include:

• Webhook trigger → validate data → create/update record in CRM
• Schedule trigger → fetch data from API → transform → store in DB/Sheet
• Event trigger → decision logic → send notification → call follow-up API

If you’re new, start with a simple trigger + action workflow and then add branching logic and error handling once the core flow is working.

Best practice is to store API keys and tokens using n8n’s credentials system rather than writing secrets directly into workflow fields. This centralizes secrets, reduces accidental exposure in exports, and makes management easier.

Security tips: rotate keys periodically, use separate credentials for testing vs production, and avoid placing secrets in notes or debug logs. If an integration uses OAuth, use the official OAuth method where possible since it provides better controls and revocation.

Yes. You can export workflows from your current environment and import them into this hosted workspace. After importing, you typically reconnect credentials (each environment stores secrets separately) and confirm that triggers like webhooks and schedules are set correctly.

A safe migration approach is: import → reconnect credentials → run test executions with sample payloads → enable production triggers. This avoids duplicate runs and ensures everything behaves as expected before going fully live.

If you’re hitting the limit, it means your automation usage is growing. You have two smart options: optimize your workflows to reduce unnecessary runs, or upgrade to a higher tier with more execution capacity.

Optimization ideas: filter events early, combine multiple small workflows into one workflow with branches, reduce polling frequency, and batch API calls or writes when possible. These changes often reduce executions while improving reliability.

Reliability comes from: validating inputs, handling errors gracefully, retrying temporary failures, and alerting your team when something breaks. For example, if an API is rate-limiting, retries with backoff can prevent workflow failures.

It also helps to keep a simple audit trail (write key results to a spreadsheet or database) so you can confirm what ran and what failed. Separating “core processing” from “notifications” also makes troubleshooting easier.

Yes. You can invite an unlimited number of users. This is great for teams where multiple people build, review, and maintain automations. For best collaboration, use consistent naming conventions, organize workflows into folders, and keep a “test” area for experiments.

For production workflows, consider a simple review process: make changes in a test workflow, validate results, then apply to the production workflow.

Provisioning is designed to be quick. After activation, log in, set up your first credentials, and build a starter workflow. Most users start with a schedule trigger or webhook trigger and a single action (email, Slack, webhook call, etc.).

If you need quick guidance, your internal docs can be linked from the Knowledge Base page. Start small, confirm it works, then expand.

Support can help with provisioning, access, connectivity issues, and common workflow troubleshooting. When contacting support, include: workflow name, node name where it fails, approximate timestamp, and the full error message.

This helps engineers identify whether it’s a credential issue, an API limitation, a rate limit, a webhook payload mismatch, or a network connectivity problem.