When did usage jump?
Daily credit burn across the billing cycle - not one opaque monthly total.
WEXTL® Analytics shows how your organization spends its plan [1] - workflow credits, data transfer, and AI assistant usage, day by day across the billing cycle. Credits left, average per day, and the reset date visible on the chart, to track what automations actually consume.
WEXTL® connects the numbers to the work behind them. Spotted unusual spike - open the run history [2] of that workflow and check which run caused it - or the Audit log [4] to see who from your team worked on automations recently.

Built for planning, not for debugging - that happens in run history [2]. Here are 4 questions customers answer [3] with WEXTL® Analytics.
Daily credit burn across the billing cycle - not one opaque monthly total.
Credits, data MB, and AI assistant usage plot side by side - spikes are obvious.
Credits left, average per day, and a projection before the reset date.
Workflow consumption list ranks the automations that used the most credits.
Credit usage is counted in 3 simple steps - from a single run to a forecast for the whole billing cycle [1]. Nothing to set up: the dashboard fills in after first runs starts to flow.
STEP 1
Workflow nodes spend plan credits, and data moving between them counts as transfer in MB. Each run shows its own spend in run history [2].
STEP 2
Credits, data transfer, and AI assistant usage are plotted day by day across the current billing cycle - a predictable trend line, not just monthly total.
STEP 3
Credits left, average per day, and a projection for the whole cycle sit above the chart - enough to know how your billing cycle may end.
Workflow credits, data transfer, and AI assistant credits are three separate lines on one chart - each on its own scale, so a small AI line never gets flattened by a large credit line. Hover over on any day - and you can read all three numbers at once.
This is how you tell two different spikes apart. A credit spike usually means a workflow ran more often than planned. Data spike may indicate a large file was processed [3].
Once you know the day, go one level deeper. The workflow consumption list below the chart shows which workflow spent the most, and its run history [2] shows the exact run, such as a retry loop on every webhook delivery.
Start tracking today
The stat cards answer it without a separate billing page: credits left, average credits per day, active workflows, and days until the subscription resets [1]. The average comes with a projection for the full cycle, so "are we on budget?" answer is clearly visible.
A sudden jump in the projection usually follows a change - a new workflow, a shorter schedule interval, a wider trigger. The Audit log [4] shows who made that change and when, to compare it against the day the chart moved.
Org admins see the same chart and stat cards on the admin view of the organization - one widget for the whole team.
Start building today
No. AI Agent nodes inside a workflow spend regular workflow credits, like any other node. The AI credits line tracks the AI assistant that builds workflows with you, and it has its own balance.
Analytics answers "how much did the org use, and when?". Run history answers "what did this one run do, and what did it cost?". Use the chart to find the day, then the workflow run history to find the run.
Analytics shows usage numbers. The Audit log (Dashboard → Activity) shows who changed workflows, credentials, and members. When usage jumps after a change, the Audit log tells you which change and who made it.
Yes. The admin view of an organization uses the same chart and stat cards, showing org-wide credits, data, and AI usage - not only the runs the admin started.
Check your plan on the pricing page - plans that allow it can buy extra credits instead of waiting for renewal. The projection on the stat cards is there so you see this coming days ahead.
List of references used in text part of the page about Analytics feature on WEXTL®.