Automations
An automation keeps an address supplied with energy so you stop buying it by hand. You set it up once against an address; from then on energy arrives without you.
Three things are true of all modes:
- You pay per delivery, at your price, from your TRX balance. There is no prepaid budget or envelope.
- Energy only. Bandwidth has no automations — it’s available as a one-off purchase only.
- Out of money means paused, not overdrawn. If your balance can no longer cover the next delivery, the rule pauses instead of failing. See Pausing.
Which mode do I want?
Section titled “Which mode do I want?”| If the address… | Use | Why |
|---|---|---|
| Sends in bursts, unpredictably | Auto-refill | Reacts to what’s left, not to the clock |
| Sends a steady amount every day | Auto-renewal | Cheapest when the daily need is known |
| Sends occasionally and you’d rather not tune anything | Smart | We pick the moment for you |
When in doubt, start with auto-refill — it is the one that adapts to real usage.
Auto-refill
Section titled “Auto-refill”Watches the address and tops it up whenever its energy falls below a threshold you set. You choose the threshold, how much to deliver, and the rental period.
Best for wallets whose activity you can’t predict: it only spends when the address has actually drained.
Auto-renewal
Section titled “Auto-renewal”Renews a fixed amount of energy once a day, no matter how much is left. No threshold to tune — just the daily amount.
Best when you know the daily need, e.g. a payout run that always sends about the same number of transfers. Because it re-rents rather than topping up, you get a predictable daily cost.
Creating the rule requires enough balance for at least one renewal.
Hands the timing to us: we watch the address and deliver when we decide it needs energy — for instance right before a transfer — rather than on a threshold or a schedule.
Each delivery is roughly 131,000 energy (about two transfers’ worth), delivered in one go. Enabling requires enough balance for one delivery.
Best when you want it to just work and don’t want to think about thresholds or periods.
What it costs
Section titled “What it costs”You’re billed per firing, at your price, for what was actually delivered — so the cost tracks real usage, not a subscription. Before creating a rule, the form previews what a single firing costs.
A rough sense of it: an auto-refill that fires three times a day costs three deliveries. Smart charges you only when a delivery is due.
Pausing and auto-resume
Section titled “Pausing and auto-resume”A rule stops for one of two reasons, and the difference matters:
- You paused it — only you can start it again. Auto-resume will not touch it.
- We paused it (your balance couldn’t cover the next delivery) — this is the one auto-resume is for.
Turn on auto-resume when you create the rule and a system-paused rule comes back by itself once you top up enough to cover a delivery. Leave it off and it waits for you.
Either way you get a notification in the dashboard the moment a rule pauses or resumes, so a silent stop
is not a thing that happens to you. You can receive the same events as
webhooks (automation.paused, automation.resumed) if you’d rather your own systems
knew.
Resuming needs balance. A rule won’t resume into a balance that can’t cover one more firing — it would just pause again.
Cancelling vs pausing
Section titled “Cancelling vs pausing”Pause is reversible; the rule keeps its settings and waits. Cancel is final — a cancelled rule can’t be resumed, and you’d create a new one instead. If you’re unsure, pause.