Skip to main content
Credits power Flowla’s workflows and AI features. Each time a workflow action runs successfully, it uses a credit. Standard actions use 1 credit, AI actions use 2. Credits renew monthly with your billing cycle. You can check your current usage at the bottom of the left sidebar.

​
Workflow credit usage

Only successful actions consume credits. If an action fails, you won’t be charged.

​
Asset intelligence credit usage

Generating asset intelligence on a library asset is metered differently from workflow actions, because it involves parsing and analysing a whole file rather than running a single step. Bigger or longer assets therefore cost more, almost entirely because of the parsing step.
If your organisation doesn’t have enough credit balance to cover generation, it’s skipped rather than run partway. Turning on Auto-generate asset intelligence for a large existing library is a real one-time spend, worth knowing before you flip it on.
REX Chat and signal generation do not currently spend organisation credits. Asset intelligence generation is the one REX feature that’s metered. REX Chat does require your organisation to have an available credit balance in order to run.

​
Viewing your credits

Check your credit status at the bottom of the left sidebar:
  • Current usage — Credits used this billing period
  • Credit limit — Total credits available
  • Reset date — When credits renew

​
What happens when you run out

When your organisation’s credits are exhausted:
  1. Workflows pause — Active workflows stop executing
  2. Queued actions wait — Pending actions remain queued until credits renew
  3. Triggers still fire — Events are captured, but actions don’t run
  4. Credits renew monthly — Full allocation is restored on your billing date
If you need credits before your renewal date, contact support to upgrade your credit package.

​
Credit limits by plan

Learn more about available plans and features to find the right fit.

​
Tips to reduce credit usage

​
Filter your triggers

Configure triggers to only run for relevant objects. Use conditions to prevent unnecessary workflow runs.

​
Use break actions

Add conditional break actions to stop workflows early when criteria aren’t met, preventing downstream actions from consuming credits.

​
Consolidate actions

Combine multiple small workflows into efficient larger ones where possible.

​
Review workflow analytics

Monitor which workflows consume the most credits and optimise high-usage ones.

​
Book a workshop

Schedule a session with our team to optimise your workflows and reduce credit consumption.