Do Workout

Review your workout progress

Category: Pending
Primary Subcategory: Pending

Integration details

Description

Connect your Do Workout account to ChatGPT to review your training, understand your progress, check your schedule and programs, and get practical suggestions based on your workout history. You can also create program change proposals for review in Do Workout. Changes are applied only after you explicitly accept them.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-09-23
Tool count: 17
Geography: US

ChatGPT Plugin Discovery Score

ChatGPT Plugin discovery is coming soon

ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.

No spam. Unsubscribe any time.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Do Workout has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

17 tools agents can invoke

Slim dashboard KPIs and recovery summary. Prefer get_training_status for "what to do today" and get_program_status for per-program progression detail. Host must supply IANA timezone (e.g. Europe/Kyiv) via time_zone or tools/call _meta.clientContext.timezone. Do not ask the human. Do not invent today from raw logs — call this view.
get_dashboard_summary
Read set-by-set history for one exercise_id (from list_exercises or a program template). For whole-session history use get_workout_history; for program trends use get_training_progress.
get_exercise_history
Fetch one full program template by program_id (from list_programs). Payload can be large — prefer list_programs when only titles, ids, or revision are needed.
get_program
Returns the typed contract for propose_program_changes changes[]: every change.type, required/optional fields, workout refs (clientWorkoutKey), scheduleConfig (weeklyDays.dayOfWeek 0–6, daysOfWeek sugar), and worked examples. Use it before composing changes[] if it has not already been retrieved. The schema is stable for the current deployment and can be reused during the conversation; do not refetch unless there is reason to believe the contract changed. It applies to propose_program_changes and is not required for propose_program_creation.
get_program_change_command_schema
Per-program progression and deload/recovery status (like Calendar program status cards). Use for "how is my progression / recovery week?"; not for picking today's workout (get_training_status) or date-range schedule (get_week_schedule). Host must supply IANA timezone (e.g. Europe/Kyiv) via time_zone or tools/call _meta.clientContext.timezone. Do not ask the human. Do not invent today from raw logs — call this view.
get_program_status
Read one user-owned proposal by request_id (status, preview, result). Does not accept, reject, or apply changes — the user does that in the Do Workout app.
get_training_change_request
Return units, defaults, equipment profiles, merged progression profiles, timers, and design limits for building or proposing programs. Use include to retrieve only needed sections where practical: equipment, defaults, progressionProfiles, timers, limits. The response versions identify the current profile, progression catalog, and timer catalog inputs. Normally reuse the result during the same interaction; do not repeatedly refetch unless relevant configuration or version information indicates it changed.
get_training_configuration_options
Bounded progress aggregates for one program over a date range (sessions, volume, load/e1RM trends, soft signals). Requires program_id, from_date, to_date. Not a substitute for raw history tools or Home "what to do today" (get_training_status). Host must supply IANA timezone (e.g. Europe/Kyiv) via time_zone or tools/call _meta.clientContext.timezone. Do not ask the human. Do not invent today from raw logs — call this view.
get_training_progress
Answer "what should I train today?" — next action and consistency signals (same coaching brain as the app Home). Prefer this over inventing today from get_workout_history. Not the calendar range view (get_week_schedule) or dashboard KPIs (get_dashboard_summary). Host must supply IANA timezone (e.g. Europe/Kyiv) via time_zone or tools/call _meta.clientContext.timezone. Do not ask the human. Do not invent today from raw logs — call this view.
get_training_status
Read the authenticated user's workout-relevant profile (units, language, schedule/progression/equipment defaults, optional body metrics). Use before designing or proposing programs.
get_user_profile
Scheduled workouts for a from_date–to_date calendar range. Use for "what is on my schedule this week?"; not for Home next-action (get_training_status) or progression/deload cards (get_program_status). Host must supply IANA timezone (e.g. Europe/Kyiv) via time_zone or tools/call _meta.clientContext.timezone. Do not ask the human. Do not invent today from raw logs — call this view.
get_week_schedule
Read recent completed workout session logs (dates, volume, notes). For "what should I train today?" use get_training_status instead of inventing from history.
get_workout_history
Search the merged Do Workout system + user exercise catalog when exercise IDs are not already available from get_program, prior list_exercises calls, or other Do Workout tool results. Reuse returned IDs; do not re-query merely to verify them because proposal tools validate referenced exercise IDs server-side. Prefer one broad filtered search with an appropriate limit over many single-exercise text searches; paginate only when current results are insufficient, use exclude_exercise_ids to avoid duplicates, and call this tool sparingly while building a program.
list_exercises
List training program summaries for the authenticated user (id, title, workout names, revision, progression flags). Call this first to obtain program_id and revision for get_program or propose_program_changes.
list_programs
List the authenticated user's AI program proposals (default statuses: pending). Use after propose_* to check status; never claim the program was updated until status is accepted.
list_training_change_requests
Creates a pending proposal in Do Workout (TrainingChangeRequest + in-app notification). Does NOT modify the Program. The user must Accept or Reject in the Do Workout app; only Accept applies changes. Never tell the user the program was updated after this tool alone. Requires program_id and expected_revision from list_programs or get_program, plus title, summary, changes[], and idempotency_key (16–128 chars). Referenced catalog/configuration IDs are validated by Do Workout when the proposal is created. After transport uncertainty, retry with the SAME idempotency_key; a new key may create a separate pending proposal. Call get_program_change_command_schema before composing changes[] (all types, fields, clientWorkoutKey workout refs, examples). Each item: { change: { type, ...fields }, reason }. addWorkout: set clientWorkoutKey; reuse it as workoutId / in reorderWorkouts.workoutIds in the SAME proposal.
propose_program_changes
Creates a pending new-program proposal in Do Workout (TrainingChangeRequest + notification). Does NOT create the Program. The user must Accept or Reject in the Do Workout app; only Accept creates it. Never tell the user the program exists after this tool alone. Gather enough context first and reuse exercise IDs from prior Do Workout results. Call list_exercises only for missing IDs, preferring one or a few broad searches; do not make per-exercise verification calls. Requires proposal title, summary, idempotency_key (16–128 chars), and a complete definition shaped as {title, workouts:[{name?, clientWorkoutKey?, exercises:[{exerciseId, prescription?, progression?}], timers?}], schedule?, progression?}. Referenced catalog/configuration IDs are validated by Do Workout when the proposal is created. Once the definition is complete, create the proposal. After transport uncertainty, retry with the SAME idempotency_key; a new key may create a separate pending proposal.
propose_program_creation

Do Workout FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.

Get alerts for Do Workout

ChatGPT Plugin discovery is coming soon

Competitive lineup

17 tools agents can invoke