Credits only matter when they run out at the wrong moment — an overnight loop that stops halfway, a review that never posts. Automatic top-up exists to make that impossible without handing us a blank cheque.
It is available to every organisation and it is off by default. Nothing is ever charged automatically until an Owner or Admin turns it on.
Turning it on
From the organisation's billing page, an Owner or Admin:
- Saves a card (stored by our payment provider, never by us).
- Chooses a threshold — the balance at which a refill should trigger.
- Chooses an amount — how much to buy each time it triggers.
A sensible starting point is a threshold covering a day or two of your usual agent time, and an amount covering a few weeks. Both are editable at any time, and switching automatic top-up back off stops all further automatic charges immediately.
How a refill happens
The balance is checked after each run is charged. If it has fallen below your threshold, TaskGoblin charges the saved card for your configured amount and the credits appear on the balance with an entry in your billing history, exactly like a manual purchase.
Two behaviours are worth knowing:
- One refill at a time. Many goblins can be working in parallel, and several of them can push the balance below the threshold in the same moment. Only one top-up is ever in flight — concurrent runs cannot stampede your card.
- A declined card does not loop. If the charge fails, the failure is recorded and surfaced on the billing page, and no retry storm follows. The organisation falls back to the normal behaviour at zero balance: work already underway finishes, new runs wait until you top up manually or fix the card.
Do I need it?
No. Manual top-ups are perfectly workable, credits never expire, and there is no discount attached to automating it. Turn it on when unattended work — scheduled loops, automatic reviews, overnight triage — is doing enough for you that a stalled queue would be noticed the next morning.
Where to go next
- Pricing and credits — what a run costs and how the balance is spent.
- Schedule loops — the unattended runs that benefit most from a balance that refills itself.