Skip to main content
FlowFn
IntegrationsTemplatesPricingDocsBlogSign inStart free
All posts
BillingCreditsCost-GuardTutorial

The Money Layer — Billing, Credits & Cost Guards in FlowFn

Everything you build eventually runs, and running costs something. FlowFn meters that with credits, caps it with plan limits, and — crucially for anything public — protects it with cost guards so a viral form or a runaway bot can't drain your account. This is the one page that answers "what am I spending, what are my limits, and what happens when I hit them?"

FlowFn Team · Product

16 Jul 2026 · 4 min read

The Billing page is the money dashboard. Its default Usage tab tells you three things at a glance — your plan, your credit balance, and how much of your plan you've used:

The Billing Usage tab: current plan, credits, and plan-usage bars

Let's unpack each.


Credits: what runs costs

Credits are FlowFn's unit of consumption. They're spent when things run:

  • a workflow run or agent run (a small base fee plus per-step costs),
  • platform AI on FlowFn's shared key (metered by tokens),
  • a platform-tool call (Slack, Stripe, …), a public playground action, an external MCP tool call.

They roll over until they expire, your plan grants a batch each cycle, and you can Top up any time. One important rule: for team-owned work, credits are charged to the team owner — so a public form your teammate built spends your credits if you own the team. (And remember from the BYOK post: AI on your own key doesn't touch credits at all.)

Every debit and grant is recorded in an append-only ledger (the View credits link), so you can always see exactly where credits went.


Plan usage: your limits

Below the balance, the Plan Usage card shows a bar for every limit your plan sets — workflows, apps, forms, agents, streams, concurrent runs, monthly platform-AI credits, and more — each as used / cap:

The bars are color-aware: they warm to amber past ~75% and go red past ~90%, so you can see what you're about to outgrow before you hit it. An unlimited cap shows . This is the fast way to answer "can I make one more agent?" or "am I about to run out of AI credits this month?"


Cost guards: protecting your public surfaces

Here's the part that matters most once your app is live. Anything a stranger can hit — a public playground, a form, a visualizer, an agent widget, a stream, a webhook, an MCP server — can be driven by third-party traffic you don't control. Cost guards put a daily ceiling on each of those, per resource:

The Public usage limits card: per-surface daily caps, with one resource paused

Each public surface has a daily cap, and the card shows this month's usage against it. When a resource crosses its daily cap, new requests get a rate-limit response that clears on its own at the next daily reset. If traffic keeps hammering it well past the cap, a breaker trips and pauses the resource entirely until the reset (or an upgrade) — and that hard-paused state is what the 1 paused badge counts. Here, a runaway playground has tripped it, and the banner explains it'll resume automatically.

The mechanics are worth knowing: as a resource approaches its cap you (the owner) get a budget alert; at the cap it returns a rate-limit error to visitors; and far past it, a "panic" breaker hard-pauses the resource immediately rather than letting the overage keep climbing. It's the difference between "my form got popular and cost me $40 overnight" and "my form hit its limit and paused itself." The guard is the safety net under everything you make public.


The rest of the page

Three more tabs round it out: Plans (compare tiers and upgrade/downgrade), Payments (your cards and invoice history, via Stripe), and Coupons (any discount codes issued to you). And because billing is a real team responsibility, it's a delegable role — you can give someone the Billing role so they manage this page without touching your workflows (see Teams & roles).


Wrap-up

FlowFn's money layer is three ideas working together: credits meter what you run and roll over until they expire; plan limits cap how much you can build (shown as friendly usage bars); and cost guards put a daily ceiling on every public surface so third-party traffic can pause a resource instead of draining your account. Charges land on the team owner, and BYOK AI stays off the meter entirely.

Open your Billing page, glance at the Plan Usage bars to see what you're close to outgrowing, and check the Public usage limits before you promote anything with a public URL — that's the habit that keeps surprises off your invoice.

And that wraps the series. From your first workflow to the App that hosts it, the integrations it calls, the runs you inspect, and the credits it spends — you've now got the whole platform. Know what it costs, cap what it can spend, and ship without holding your breath.

Read next

Use-Case
SAAS
Auth

Build a Client Portal with FlowFn

Agencies, consultancies, and B2B teams all hit the same wall: clients want a single place to check their projects, invoices, and files — and emailing PDFs back and forth doesn't scale. A client portal fixes it, but building multi-tenant auth (each client sees only their own data) usually means real engineering. In FlowFn it doesn't: end-user sign-in, per-client data scoping, and a polished portal page are features you assemble, not code you write.

FlowFn Team · 16 Jul 2026 · 3 min read

Use-Case
Devops
Automation

Build an Incident Alerting & On-Call System with FlowFn

When something breaks at 3am, the difference between a blip and an outage is how fast the right person's phone buzzes. You don't need a pricey incident-management platform to get there. FlowFn can catch an alert from any monitor, log the incident, page whoever's on call, escalate if they don't answer, and show the whole team a live status board — built from a webhook, a workflow, a Data Sheet, and a dashboard.

FlowFn Team · 16 Jul 2026 · 3 min read

Use-Case
Internal-Tools
Automation

Build an Internal Ops Tool with FlowFn

Every company runs on a pile of small approvals — refunds, access requests, expenses, discounts — and most of them live in a shared spreadsheet plus a Slack thread nobody can audit. An internal ops tool fixes that: one private table your team works from, action buttons that approve or reject in a click, automatic notifications, and a queue board so nothing rots. FlowFn lets you build it in an afternoon — no internal-tools platform, no login wall to wire up.

FlowFn Team · 16 Jul 2026 · 3 min read

Build your first workflow today

Start free — connect your apps, add AI, and ship an automation you can actually maintain. No credit card required.

Get started free