Today
- Followed—
- Unfollowed—
- Liked back—
Last 7 days
- Followed—
- Unfollowed—
- Liked back—
- Follow-back rate—
All time
- Total followed—
- Total unfollowed—
- Total liked back—
- Currently following—
Per-tier conversion (last 30 days)
| Tier | Attempted | Reciprocated | Active | Rate |
|---|
Higher rate = better source. Use this to tune tier_weights in settings.
Last run
—
Edit, click Copy JSON, then Open editor to paste it into GitHub. We can't write directly without a PAT.
Generated JSON
One-time setup per account
-
Capture a refresh token from your Hevy session.
- Open hevy.com and log in.
- Open DevTools → Application → Cookies → select
hevy.com. - Copy the value of
auth2.0-token(it's ~210 chars).
-
Add it as a GitHub Actions secret.
- In this repo: Settings → Secrets and variables → Actions → New repository secret.
- Name:
HEVY_REFRESH_(e.g.HEVY_REFRESH_TIM). - Value: the cookie you copied.
-
Edit your settings.json.
Set
hevy_username, setenabled: true, tune caps. Save via the Settings tab here. - Verify the token. Actions tab → Check Hevy Token workflow → Run workflow → enter your account name. A green check means the secret is valid.
- Let it run. The bot runs daily at 05:00 UTC. You can also trigger it manually via the Hevy Bot workflow.
Adding a new account
- Create
accounts/<name>/settings.json(copyaccounts/brother/settings.jsonas a template). - Add the secret
HEVY_REFRESH_<NAME>. - Add
<name>to the matrix in.github/workflows/run-bot.yml. - Add
<name>toACCOUNTSindocs/app.js.
Reading state from a private repo
If your repo is private, this dashboard needs a fine-grained read-only PAT (Contents:Read on this repo only). Paste it below — it stays in this browser's localStorage.