HUBNET · OPERATIONS
Phone Automation
Runtime and transfer activity
Admin controls
Sign in to monitor
Use the Production ADMIN_TOKEN from Coolify. After you connect, this browser tab remembers it for reloads and clears it when you disconnect or close the tab. Do not use shared devices.
PRIVATE AUTOMATION
Automation workspace
A clear view of your phone, queue and transfer activity.
Runtime
Waiting for data…
Monitor the phone and request worker start or stop remotely. Android Accessibility must already be enabled on the phone.
Start and stop are remote requests, not Android permission controls. Start may take effect when the phone reconnects; the phone must have Accessibility enabled, be paired, have required permissions, exactly one active SIM, and be unlocked. Starting does not change live mode or queue pause. A stop prevents new claims and lets an active transfer finish before stopping.
Pausing stops new phone claims but the API stays online and accepts requests into the queue. Queued live transfers may start when you resume. Uncertain transfers still block new requests and require reconciliation.
USSD flow settings
Expand to adjust menu selections and prompt detection
Adjust menu selections and prompt-detection phrases for the fixed MTN *171# flow. The number, amount, and reference are filled automatically from each API request.
Immediately after entering the API reference, the worker waits for the PIN prompt, obtains one-time server authorization, and automatically enters the PIN from that same API request. It does not wait for a separate review step. If the PIN prompt also displays transfer details or fees, the worker checks those against the request before submission. Changes apply to the next claimed job and cannot be saved while a transfer is active.
Status webhooks
Configure an HTTPS receiver to push transfer updates to your project.
Deliveries are signed with your shared secret. Keep it private and configure the same secret in your receiving project. The webhook payload never contains a PIN.
Transfer history
Latest records
| Select | Created | Updated | Reference | Provider transaction ID | Recipient | Amount | Mode | Status | Step / detail | Action |
|---|
Retry failed transfer
Retry requeues failed or cancelled transfers using their original references and a fresh 15-minute queue window. Only pre-PIN failures and unclaimed cancellations can be retried here; uncertain transfers cannot. Live retries remain queued while the queue is paused. Verify every recipient and amount, and never retry if you are unsure whether a transfer completed.
Reconcile uncertain transfer
First check the wallet/provider history independently. Choose “Succeeded” only if you confirmed the transfer completed; choose “Failed” only if you confirmed it did not. A provider transaction ID can be recorded for a verified success. This records your finding and never retries or sends money.
Refreshes every 5 seconds. Queue controls do not turn live transfers on or off. Never treat “simulated” as proof of payment. To install on Android, use Install app or Chrome’s menu → Install app.