Costs

Every paid action in GTM Goat runs on credits — a single balance per workspace, regardless of which provider billed in the background.

Success-based billing

Credits are reserved when a run starts and only actually deducted on success; if an action fails, the reservation is released — you never pay for an enrichment that delivered no value, or an AI response that counts as failed instead of being stored.

Cost cap per run

A cap limits what a single run may spend. When a run reaches it, it halts before the next step — visibly, with the reason and both numbers. Steps already completed stand; nothing is rolled back.

Where it applies differs, and knowing that is more useful than a blanket promise:

• Table runs require one for any paid effect. Without a cap, a paid run does not start at all.
• Workflow runs accept one at start (max_credits). Without it the workflow runs uncapped — set it wherever a workflow iterates over many rows.
• Individual cells carry their cost visibly anyway (see below) and need no cap of their own.

What is measured is the workspace’s spend across the run. If several automations of the same workspace run at once, the cap attributes too much rather than too little — a brake that stops early is the right direction.

BYOK: bring your own key

For categories like research or enrichment, you can supply your own API key (bring your own key). Actions through that key bypass your credit balance — you pay your provider directly, the platform doesn’t bill anything extra for that category.

Where you see costs

Every Cell carries its own cost; every Run shows the sum of its cells or line items. Nothing gets billed without you being able to see afterward exactly what for.

See also: Approvals — the cost cap is part of what you review when approving a run.