n8n Cloud Introduces Top-Ups and Dashboard Tracking for Assistant Credits

n8n Cloud Introduces Top-Ups and Dashboard Tracking for Assistant Credits n8n has introduced credit top-ups for Starter and Pro Cloud users, enabling customers to purchase additional n8n Assistant credits rather than waiting for monthly plan allowances to reset. Cloud Starter and Pro users can now purchase extra Assistant credits manually or via automated top-ups with monthly spending caps. Purchased extra credits roll over across months, expiring 12 months after purchase, and are used only after the monthly included allowance is exhausted. A new dashboard tab provides visibility into credit balances, usage charts, top-up history, and team member consumption. Monthly credit allowances have been recalibrated alongside an internal upgrade to a newer model and fixed standard credit valuation. Top-Up Mechanism and Expiration Paid Cloud users can top up Assistant credits manually by purchasing packages or automatically by configuring balance triggers and refill amounts with a default monthly cap. The platform continues to supply an included monthly allowance resetting on the 1st of each month. Included credits are consumed first, after which extra credits are used; these purchased credits roll over monthly and remain valid for 12 months. Usage Visibility and Allowance Updates A new Assistant credits tab in the Cloud admin dashboard tracks total balance by included and extra credits, displays spend charts across 24-hour to 30-day windows, and lists top-up history and top users. Within the editor, the Assistant warns users when credits hit 10%. Furthermore, monthly plan allowances have been adjusted to match a standardized credit value and a newer model that reduces the credits required per task. Consumption Benchmarks and Operational Rules Credit costs vary based on prompt specificity and context: quick questions generally cost 10–20 credits, simple single-prompt workflows use 50–100 credits, and complex builds or debugging range between 300–600 credits. All users on an instance share the credit pool, though only instance owners on paid plans can purchase top-ups. Executing workflows does not consume Assistant credits, and Assistant credits remain distinct from AI Gateway credits.

n8n Cloud 推出 Assistant 点数充值与自动补充功能 n8n 宣布面向 Starter 和 Pro 云端订阅用户开放 Assistant 点数充值功能，提供手动购买与自动补充选项，同时调整了每月自带配额并上线了点数使用监控面板。 n8n Cloud 订阅用户现可手动或设置自动充值额外 Assistant 点数，额外点数结转有效并于 12 个月后过期。 系统将优先消耗每月包含的自带配额，且仅实例所有者在有效付费方案下有权执行充值。 官方迁移至新模型并统一了点数价值，同时推出控制台面板以追踪用量、消耗图表及成员使用排行。 工作流运行本身不消耗 Assistant 点数，Assistant 点数与运行工作流 AI 调用的 Gateway 点数各自独立。 充值方式与额度消耗规则 订阅用户可通过手动选购点数包或开启自动充值来获取额外点数。自动充值支持自定义触发阈值、补齐目标及默认开启的每月消费上限。系统始终优先扣除每月 1 日重置的基础包含点数，耗尽后才使用充值点数；购买的额外点数可逐月结转，有效期为 12 个月。 配额更新与用量监控面板 随着模型升级和内部机制优化，Starter 与 Pro 用户的每月点数额度已做调整，统一了各付费方案下的点数标准价值。管理面板新增了 Assistant 点数标签页，可查看包含点数与额外点数余额、最长 30 天的消耗图表、实例内高频使用成员列表及充值记录；编辑器内也支持显示单次对话消耗并在剩余 10% 时发出警示。 场景参考与核心使用细则 常规咨询单次约消耗 10 至 20 点，简单工作流或修复需 50 至 100 点，复杂构建与长调试约需 300 至 600 点。实例内所有成员共享点数池，且仅所有者可充值。此外，运行工作流不消耗 Assistant 点数，其与工作流调用 AI 模型的 Gateway 点数相互独立；试用期提供 800 点且不支持充值，自托管版本则使用自备模型账户。

Starting today, if you're on n8n Cloud (Starter or Pro) and you run out of Assistant credits, you can buy more and keep building. Being able to top up has been one of the most common requests we've heard since we launched n8n Assistant. Until now, running out meant waiting for your allowance to reset on the 1st of the month, or upgrading your plan. Neither is a great option when you're halfway through building a workflow. How top-ups work Your plan still includes a monthly allowance of Assistant credits that resets on the 1st of the month. Top-ups are extra credits on top of that, and they're optional. You can add extra credits in two ways: Top up manually. Pick a credit package whenever you need one. Turn on auto top-up. Choose the extra-credit balance that triggers a top-up and the balance to refill to. A monthly limit, on by default, caps how much auto top-up can charge in a month. The Assistant always uses your included credits first, and only moves on to extra credits once those run out. Extra credits carry over from month to month and expire 12 months after you buy them. See where your credits go The new Assistant credits tab in the Cloud admin dashboard shows: Your balance, split into included and extra credits A spend chart for the last 24 hours, 7 days, or 30 days Which users on your instance use the most credits Your top-up history In the editor, the Assistant panel shows how many credits the current conversation has used, and warns you when you're down to 10%. We've updated your monthly credits If you're on Starter or Pro, you'll notice that your monthly credit allowance has changed. For most people, the updated allowance will go further than before. That comes down to some improvements we’ve made: A newer, more capable model. We've moved everyone to a newer model, so the Assistant needs fewer credits to do the same work. One standard credit value. Now that you can buy credits, a credit needs a fixed price. We recalibrated credits so they're worth the same on every paid plan, and set each plan's allowance to match. Improvements under the hood. We've optimized how the Assistant works internally, so it gets more done with each request. How many credits does it take to build a workflow? That's the question we get most often, and there's no single answer. It depends on the request: longer conversations, more complex workflows, and debugging sessions use more credits than short, focused requests. No two prompts will cost the same, due to non-deterministic LLM behavior and different surrounding context. What we can provide is a is a sense of the range to expect. Here are what a few typical requests use today: A quick question \[10-20 Credits\] "What authentication methods for Slack does n8n Support?" A simple workflow or fix from one prompt \[50-100 credits\] "Once a day, check the weather in Berlin using a free weather API and email me the forecast." A larger build with explicit testing, or a longer debugging session \[300-600 credits\] “Before building, research the current docs for free keyless APIs for geocoding, weather forecasts, country info and exchange rates, and pick three real destinations with very different weather this week so each one lands in a different trip category. Then build a "Travel Weather Briefing" workflow: a form asks for a city, travel dates and home currency, the APIs above gather the data, writes packing tips, labels the trip Hot, Cold, Wet or Mild, and each briefing is saved to a Data Table. Post the briefing to a Slack channel, show it on the form's completion page. Ensure you handle errors such as unknown cities or currencies, and test the workflow with the three cities you researched.” These ranges will change as we keep improving the Assistant and the models behind it, so treat them as a rough guide. One tip that definitely helps: specific prompts use fewer credits than open-ended ones. A few things to know Credits are shared across your instance. Everyone on the instance draws from the same balance. If five people on your team use the Assistant, they're all using the same pool, and the top users view shows who's using what. Only the instance owner can top up. Topping up also requires an active paid plan. Your workflows keep running. Running a workflow never uses Assistant credits, even if the Assistant built it. Only your conversations with the Assistant do. Assistant credits and Gateway credits are separate. Assistant credits pay for your conversations with the Assistant. Gateway credits pay for the AI model calls your workflows and agents make when they run. Topping up one doesn't add to the other. Free trials include a one-time allowance. Free trials get 800 credits. Top-ups aren't available during a trial, so you’ll need to upgrade to a paid plan to get more. Self-hosted n8n doesn't use Assistant credits. The Assistant runs on your own model provider account instead.