Hevy integration

Last updated: August 13, 2026

What the integration does

COORDINATOR is a coordination workspace with an AI layer that reads across the systems you connect. Connecting Hevy lets that layer see your lifting — which sessions you did, which lifts, at what weight and volume — so it can answer questions and plan around the work you actually put in.

Once connected, COORDINATOR can:

• Show your recent Hevy workouts alongside the rest of your workspace.
• Summarize strength trends when you ask ("how much did I squat this month?", "am I adding volume?").
• Read the routines you've saved in Hevy, so it can talk about your actual program.
• Build routines and write them into your Hevy account, so a plan you work out in chat lands in the app you train with.
• Trigger automations you set up yourself — routines in COORDINATOR that run when a new workout syncs.

What COORDINATOR reads, and what it writes

Hevy is one of only two integrations COORDINATOR can write to. The split matters, so it's worth being precise:

So your training history is never touched. Your routines — the templates you train from — can be changed, but only when you ask for it.

What data we receive

Your Hevy workout records and their contents: session date and duration, exercises performed, and the sets, reps, and weights logged against them. We also read your saved routines and folders, and Hevy's exercise catalog so we can match exercise names correctly. We do not receive your Hevy password.

Hevy data is used to provide the features above, for you. We do not sell it, we do not share it with other COORDINATOR users, and we do not use it to train AI models. It is handled as sensitive health and fitness information under our Privacy Policy.

Connecting Hevy is opt-in

Nothing is connected by default, and COORDINATOR receives no Hevy data until you explicitly connect it. You opt in when you want it, you can opt out at any time, and you can reconnect later without penalty. COORDINATOR works without Hevy connected — you just won't see lifting data in it.

How to connect

Hevy doesn't offer a sign-in redirect the way Strava or Oura do, so instead of sending you to Hevy to approve access, COORDINATOR asks for an API key that you generate in Hevy yourself. A key is a revocable credential — it is not your password, and you can destroy it on Hevy's side at any moment.

1. Sign in to COORDINATOR.
2. Go to Settings → Integrations.
3. Find Hevy under Wearables and select Connect.
4. COORDINATOR shows a single field asking for your Hevy API Key, with a link to where you generate it.
5. In Hevy, open Settings → Developer and generate an API key. Copy it.
6. Paste the key into COORDINATOR and submit.

We check the key against Hevy immediately. If it's valid the card shows as connected; if it isn't, nothing is saved and you'll be asked to try again. A key that fails is almost always one that was partially copied — re-copy the whole string, with no leading or trailing spaces.

To bring in workouts logged before you connected, use Sync history on the Hevy card. It pulls a window of past workouts and skips anything already imported, so running it more than once is safe.

If you can't find the developer settings page in Hevy, API key access isn't available on your Hevy plan — see Routine pushing needs Hevy's paid API access below.

Building routines from chat

Ask COORDINATOR for a training plan and it can write the result straight into Hevy as saved routines — typically one routine per training day, grouped in a folder. Each routine carries real exercises, sets, reps, loads, and rest times, not empty shells.

It writes only when you ask it to. There's no background syncing of routines, and no separate confirmation step once you've asked — agreeing to the plan in the conversation is the approval, so the routine is created at that point.

Re-pushing a plan replaces the routine

This is the one behaviour worth understanding before you use it. When COORDINATOR writes a routine whose title matches one already in your Hevy account, it updates that routine in place rather than creating a second copy. The update replaces the routine's contents wholesale — the new version is exactly what was sent, so anything not included is gone.

In practice that means:

• Asking for a revision to "Push Day A" updates your existing "Push Day A" rather than cluttering the app with duplicates. This is usually what you want.
• If you hand-edited that routine in Hevy since it was created, a re-push overwrites your edits.

If you've customised a routine in Hevy and want to keep it, either rename it there or ask COORDINATOR to use a different title for the new version. If you want your edits preserved, tell it what you changed so it includes them.

Limits

A single push writes at most 8 routines, each with at most 15 exercises, each with at most 12 sets. Anything beyond that is trimmed and COORDINATOR tells you what it left out.

Loads are stored in kilograms. If you work in pounds, values are converted on the way in, so small rounding differences against your original numbers are expected.

If an exercise name can't be matched

Every exercise is matched against Hevy's own catalog before anything is written. If one can't be matched confidently, nothing is written at all — not even the routines that were fine — and COORDINATOR comes back with the closest candidates so you can pick. This is deliberate: a partial write would leave you with a half-built program.

If that happens, confirm the exercise you meant and ask it to push again.

Routine folders

COORDINATOR can create a folder to group a program. A routine's folder is set when the routine is created and can't be changed afterwards by an update — if you need a routine in a different folder, move it in the Hevy app, or ask for it to be recreated under a new title.

Routine pushing needs Hevy's paid API access

Reading and writing both go through Hevy's API, which is available on Hevy's paid tier. If you don't have it, connecting won't work — this is Hevy's restriction, not something COORDINATOR can enable for you.

How to disconnect

You can disconnect at any time, for any reason, without contacting us.

1. Go to Settings → Integrations.
2. On the Hevy card, open the menu and select Disconnect, then confirm.

Disconnecting deletes our stored copy of your API key immediately, stops all further reading, stops COORDINATOR being able to write routines to your account, and marks the connection inactive so nothing syncs in the background.

Routines already written to Hevy stay there. They're yours — disconnecting doesn't remove them.

Important: disconnecting does not revoke the key

Unlike an OAuth integration, there's nothing for us to revoke on Hevy's side — the key is issued by Hevy and controlled entirely by you. Disconnecting in COORDINATOR removes our copy, which is what stops us reading. If you want the key itself dead, delete or regenerate it in Hevy's developer settings. We recommend doing both.

To also delete the Hevy data COORDINATOR already imported, email [email protected] from your account email address and ask us to delete it. See Privacy Policy for the full retention and deletion terms.

Rotating your key

If you regenerate your key in Hevy, our stored copy stops working and the Hevy card will report a problem. Disconnect, then connect again with the new key.

Worth knowing: because Hevy's API doesn't tell us who a key belongs to, we identify your connection from the key itself. A new key therefore looks like a new connection rather than an update to the old one. Disconnecting first keeps things tidy.

Common sync issues

A workout hasn't appeared

Hevy has to finish saving the session to its servers first. Confirm the workout is visible in the Hevy app on another device or on the web, then use Sync history on the Hevy card.

Older workouts are missing

COORDINATOR only starts receiving workouts from the moment you connect. Use Sync history to backfill.

The card says the connection has a problem

The stored key is being rejected. That means it was deleted or regenerated in Hevy, or your Hevy subscription lapsed and API access went with it. Generate a fresh key and reconnect.

A routine COORDINATOR built isn't in Hevy

Check whether it confirmed the push. If an exercise name couldn't be matched, nothing is written at all and it should have come back asking you to confirm which exercise you meant — answer that and ask it to push again. Otherwise, pull down to refresh in the Hevy app.

A routine I edited in Hevy got reverted

A re-push under the same title replaces that routine's contents wholesale, so hand-edits made in Hevy are overwritten. Rename the routine in Hevy to protect it, or tell COORDINATOR what you changed so the next version includes it.

A routine only has some of the exercises I asked for

A single routine takes at most 15 exercises and 12 sets per exercise; a single push takes at most 8 routines. Over that, the extra is trimmed and COORDINATOR reports what it dropped. Split a large program across more than one push.

The weights in my routine are slightly off

Hevy stores loads in kilograms, so pounds are converted on the way in and can round by a fraction. Adjust in the Hevy app if you need exact numbers.

Sets or weights look wrong

COORDINATOR shows what Hevy sends, including units. Check the workout in the Hevy app first — if it's wrong there too, correct it there and run Sync history. If it's right in Hevy and wrong here, that's a bug on our side; please report it.

Contact support

Email [email protected]. Write from the email address on your COORDINATOR account so we can find it, and include:

• What you expected to happen, and what happened instead.
• The date of the workout involved, and whether it appears in the Hevy app.
• Roughly when you connected Hevy, and when you last synced.

Never send us your API key or your Hevy password. We will never ask for either. If you've already sent a key to anyone, regenerate it in Hevy right away.

For privacy questions, data export, or deletion requests, see Privacy Policy. For the terms covering third-party integrations, see Terms of Service.