Health & fitness
Trainerize
Clients, programs, check-ins and messages for your Trainerize business.
14 endpoints
Coach Catalyst publishes no public API and no MCP server; its Zapier app adds clients (checked 16 Nov 2026). Cotlet runs a hosted Coach Catalyst MCP server with 25 tools that ChatGPT and Claude use in your own coach account: inbox, programs, journeys, workouts, forms and products. Every message and every change a client sees waits for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Coach Catalyst. Coach Catalyst is a trademark of its owner. If Coach Catalyst's own integrations cover what you need, use them first.
25 tools Read and write
Coach Catalyst publishes no public API: no developer documentation, API key page or API plan on its website or Help Center. Its official automation route is a Zapier app, and no Coach Catalyst MCP server or official ChatGPT or Claude connector was found.
| What you need | Zapier app | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude about your clients | No MCP server | Copy and paste | Hosted MCP server |
| Add clients from another tool | Zapier adds clients | Add Client form or CSV | add_client after your OK |
| Inbox, programs, workouts and forms | Not covered | Click through each one | 25 tools, client-facing writes ask first |
| Run from n8n or a script | Zapier only | Manual only | REST, same key |
Checked 16 Nov 2026. Sources: Coach Catalyst home page · Coach Catalyst Zapier integration · Coach Catalyst Help Center · Help: How to Add Clients · Help: Using Client Tags to Organize Clients · Help: Managing Clients (Archive, Delete and Reactivate) · Help: Assign a Client to a Coach · Help: Sending Messages to Clients · Help: All About Messages Inbox · Help: How to use filters on the Client page · Help: Using Forms and Viewing Submissions · Help: Contracts / Waivers / Agreements · Help: How To Create Free Products · Help: How to Sell Your Products · Help: Manage client Payments · Help: Creating Discounts on Products · Help: Stop a Client's Program · Help: Assign a Client to a New Program · Help: Add an element to a client's journey · Help: Move an element or workout on a client's journey · Help: Using the Lesson Editor · Help: Add a resource · Help: How to Create a New Folder · Help: How to Add a File to a Resource Folder · Help: Adding & Removing Clients from a Folder · Help: Auto-Assign Resources · Help: Bulk Add Clients to a Resource Folder · Help: Editing Welcome Email and Text · Help: How to use Reports · Help: All About Communities · Help: Create a New Exercise · Help: How To Print A Workout · Help: Set a Workout to Repeat · Help: Build Blocks, Supersets and Warm-Ups · Help: Workout & Block Templates · Help: Adding and Using Exercise Swaps · Help: Entering Sets, Reps & Details · Help: How to View Client's Workout Progress
Once, in a browser we host for you.
One address in its settings.
It drafts replies and check-ins; you approve what clients get.
Your agent works in your own signed-in Cloud Browser. Messages, program changes and anything a client sees wait for your OK. Who can see your session
Sign in to Coach Catalyst in a Cloud Browser. Open app.coachcatalyst.com/auth/sign_in in your Cotlet Cloud Browser and sign in with your own coach email and password.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Coach Catalyst lives on the shared address https://cotlet.dev/mcp/v1 with all the other apps you switch on, so one connector serves them all. Switched Coach Catalyst on after connecting? Refresh the connector and its 25 tools load.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: coach_catalyst_read Built from the Coach Catalyst Help Center: one tool per screen, several articles where one screen holds them. Library edits that no client sees run at once; everything a client sees asks first.
The Client Index with its filters and tabs, and the bulk actions that start there: add, tag, archive or reactivate, assign a coach.
This is the Client Index page that most bulk actions start from. Coach Catalyst's own tip is to sort by compliance over a date range, then message clients by how they are doing. It changes nothing and runs without asking.
MCP callcoach_catalyst_read → list_clients
REST endpointGET https://cotlet.dev/api/v1/coach-catalyst/clients
| Name | Type | Description |
|---|---|---|
| tab string | string | `active`, `recent` or `archived`. Defaults to `active`. |
| filters object | object | Program, tag, coach, compliance range and date range, as the Client Index filters offer them. |
| sort string | string | For example `compliance` to see who is doing best or worst over the dates. |
{
"tab": "active",
"date_range": "2026-11-09 to 2026-11-15",
"clients": [
{
"name": "Client A",
"program": "12-Week Strength",
"compliance": 92
},
{
"name": "Client B",
"program": "12-Week Strength",
"compliance": 61
},
{
"name": "Client C",
"program": "Habit Reset",
"compliance": 38
}
]
} The same form as Clients > Add Client. The new client gets the welcome email at once, and a welcome text if you gave a phone number, so the agent shows you the details first. Bulk CSV upload stays in the app. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → add_client
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/clients
| Name | Type | Description |
|---|---|---|
| first_name string required | string | Required by Coach Catalyst. |
| last_name string required | string | Required by Coach Catalyst. |
| email string required | string | Required by Coach Catalyst. |
| phone string | string | Only if the client should get the welcome text. |
| time_zone string | string | If you know it; the client can change it later. |
| options object | object | Optional actions: program and start date, tag, coach, community, resource folders. |
{
"first_name": "first name",
"last_name": "last name",
"email": "jane@example.com"
} {
"client": "Client D",
"email": "client.d@example.com",
"program": "12-Week Strength",
"start_date": "2026-11-23",
"coach": "Coach A",
"welcome_email": "sent"
} Archiving keeps the client's data but removes them from current programs and removes their tags; you cannot message them while they are archived. Archiving lowers your active client count, but your plan does not downgrade by itself. Permanent delete is not offered: do that in Coach Catalyst. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → archive_client
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/client/archive
| Name | Type | Description |
|---|---|---|
| action string required | string | `archive` or `reactivate`. |
| clients array required | array | Client names or emails, as list_clients returns them. Several clients run as one bulk action. |
{
"action": "action",
"clients": "clients"
} {
"action": "archive",
"clients": [
"Client E"
],
"archived": 1
} Runs the Assign to Coach(es) bulk action from the Client Index. It changes who coaches the client, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → assign_coach
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/coach/assign
| Name | Type | Description |
|---|---|---|
| clients array required | array | Client names or emails, as list_clients returns them. Several clients run as one bulk action. |
| coaches array required | array | Coach names on your Coach Catalyst account. |
{
"clients": "clients",
"coaches": "coaches"
} {
"clients": [
"Client A",
"Client B"
],
"coaches": [
"Coach B"
],
"assigned": 2
} The Inbox, Later and Done tabs, individual and bulk messages, and forms for check-ins, reviews and signed agreements.
The Messages tab is your inbox across all clients. A conversation stays in Done after you send a message and comes back to Inbox when the client replies, so `inbox` is the list of clients waiting for you. Reading does not move any conversation.
MCP callcoach_catalyst_read → read_message_inbox
REST endpointGET https://cotlet.dev/api/v1/coach-catalyst/message-inbox/read
| Name | Type | Description |
|---|---|---|
| tab string | string | `inbox`, `later` or `done`. Defaults to `inbox`. |
| client string | string | One client's thread. Leave empty for the tab's list. |
{
"tab": "inbox",
"conversations": [
{
"client": "Client B",
"last_message": "Knee felt off on split squats again",
"received": "2026-11-16T07:42:00"
},
{
"client": "Client C",
"last_message": "Can we swap Thursday to Friday?",
"received": "2026-11-15T19:10:00"
}
]
} Coach Catalyst sends individual, bulk and scheduled messages; bulk and scheduled ones are made on desktop, which is where the agent works. Every message reaches the client, so the agent shows you the text and the recipients first. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → send_client_message
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/client-messages
| Name | Type | Description |
|---|---|---|
| clients array required | array | Client names or emails, as list_clients returns them. Several clients run as one bulk action. |
| text string required | string | The message, written or from one of your templates. |
| template string | string | A saved message template to start from. |
| send_on string | string | ISO date to schedule it on the client's journey. Leave empty to send now. |
{
"clients": "clients",
"text": "text"
} {
"clients": [
"Client C"
],
"text": "Saw a quieter week. What got in the way, and what would make next week easier?",
"sent": true
} Forms collect more than yes or no: weekly check-ins, end-of-program reviews, sleep, mood or energy. Coach Catalyst's own way to run a waiver or agreement is a form with the text under a section header and a required text question titled Signature, which records a timestamp. Sending reaches the client, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → manage_forms
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/forms/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | `list_submissions`, `create` or `send`. `list_submissions` only reads. |
| form string | string | Form name. |
| questions array | array | For `create`: section headers and questions with their type, for example text, scale or number. |
| clients array | array | For `send`: whose journey gets the form. |
| date string | string | For `send`: ISO date on the journey. |
{
"action": "action"
} {
"form": "Weekly check-in",
"submissions": [
{
"client": "Client A",
"submitted": "2026-11-15",
"energy": 8,
"sleep_hours": 7.5
},
{
"client": "Client B",
"submitted": "2026-11-15",
"energy": 5,
"sleep_hours": 6
}
]
} Start or stop a program, and add or move lessons, actions, messages and workouts on one client's journey.
Runs Assign to New Program. From the start date the client gets the program's daily lessons, actions and notifications, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → assign_program
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/program/assign
| Name | Type | Description |
|---|---|---|
| clients array required | array | Client names or emails, as list_clients returns them. Several clients run as one bulk action. |
| program string required | string | A program in your program library. |
| start_date string required | string | ISO date. |
{
"clients": "clients",
"program": "program",
"start_date": "start date"
} {
"clients": [
"Client D"
],
"program": "12-Week Strength",
"start_date": "2026-11-23",
"assigned": 1
} Runs Abandon Program. The program stops immediately and the client gets no more of its daily notifications and lessons. Starting it again means assigning it anew with assign_program. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → stop_program
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/program/stop
| Name | Type | Description |
|---|---|---|
| clients array required | array | Client names or emails, as list_clients returns them. Several clients run as one bulk action. |
| program string required | string | The current or future program to stop. |
{
"clients": "clients",
"program": "program"
} {
"clients": [
"Client E"
],
"program": "Habit Reset",
"stopped": true
} Elements are what programs are made of; this adds one straight to a client's journey on the date you pick. The client sees it on that day, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → add_journey_element
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/journey-elements
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name or email, as list_clients returns it. |
| date string required | string | ISO date on the journey. |
| type string required | string | `lesson`, `action` or `message`. |
| title string required | string | An existing element, or the title of a new one. |
{
"client": "client",
"date": "date",
"type": "type",
"title": "title"
} {
"client": "Client B",
"date": "2026-11-18",
"type": "lesson",
"title": "Knee-friendly lunge options",
"added": true
} The same as dragging the element to another day in the journey. The client's plan changes, so it waits for your OK; moving it back is the same call with the dates swapped. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → move_journey_element
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/journey-element/move
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name or email, as list_clients returns it. |
| element string required | string | Title of the element. |
| from_date string required | string | ISO date it is on now. |
| to_date string required | string | ISO date to move it to. |
{
"client": "client",
"element": "element",
"from_date": "from date",
"to_date": "to date"
} {
"client": "Client C",
"element": "Lower body A",
"from_date": "2026-11-20",
"to_date": "2026-11-21",
"moved": true
} The lesson editor takes headings, lists, text styling, images, videos and PDFs, and embeds such as YouTube or Loom through its code editor. The agent pastes plain text, which the editor handles best. A lesson is edited in your library and reaches clients only through a program or journey, so this runs without asking.
MCP callcoach_catalyst_write → edit_lesson
REST endpointPATCH https://cotlet.dev/api/v1/coach-catalyst/lesson
| Name | Type | Description |
|---|---|---|
| lesson string required | string | Lesson title. |
| content string | string | New content with headings, lists, images, videos or PDFs. Leave empty to read. |
{
"lesson": "lesson"
} {
"lesson": "Protein on a busy day",
"sections": 3,
"saved": true
} Exercises and swaps, blocks and supersets, templates, repeat rules, logged sets and a printable PDF.
Exercises live in your own database for reuse. Catalog exercises are read-only, so alternatives go on your own copy. These help articles describe the new exercise library, which Coach Catalyst says may not be on every account yet. Library edits reach no client directly, so this runs without asking.
MCP callcoach_catalyst_write → manage_exercises
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/exercises/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | `create` or `set_alternatives`. |
| name string required | string | Exercise name, unique in My Exercises (archived names count). |
| description string | string | For `create`. |
| video_url string | string | For `create`. |
| alternatives array | array | For `set_alternatives`: up to 10 exercises a client may swap to. |
{
"action": "action",
"name": "Jane Doe"
} {
"name": "Box step-up",
"alternatives": [
"Reverse lunge",
"Split squat"
],
"saved": true
} The workout builder works like a spreadsheet: Sets, Reps (8, 8-10, 8 e/s, 45 sec) and a free-text Details column the client reads word for word. Superset and circuit blocks link their exercises as A1, A2. A template needs at least one block and one exercise, and is a master copy in your library, so this runs without asking.
MCP callcoach_catalyst_write → build_workout_template
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/workout-template/build
| Name | Type | Description |
|---|---|---|
| name string required | string | Workout or block template name. |
| level string | string | `workout` (a full training day) or `block` (one section). Defaults to `workout`. |
| blocks array required | array | Each block: kind (`warmup`, `block`, `superset`, `circuit`, `cooldown`), label, note and exercises with sets, reps and details (RPE, rest, load, tempo). |
{
"name": "Jane Doe",
"blocks": "blocks"
} {
"template": "Lower body A",
"blocks": [
{
"label": "Warmup",
"exercises": 3
},
{
"label": "Strength",
"exercises": 2
},
{
"label": "A",
"kind": "superset",
"exercises": 2
}
],
"saved": true
} The same as the repeat chip in the workout's top bar, which then reads back the rule, for example Weekly · MWF · 4×. The client sees every scheduled day, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → schedule_repeating_workout
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/repeating-workout/schedule
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name or email, as list_clients returns it. |
| workout string required | string | Workout on the journey or a template. |
| start_date string required | string | ISO date of the first occurrence. |
| every_weeks number | number | Defaults to 1. |
| days array required | array | Weekdays, for example M, W, F. |
| occurrences number required | number | Total occurrences, for example 12 for MWF over four weeks. |
{
"client": "Client D",
"workout": "Lower body A",
"start_date": "2026-11-23",
"every_weeks": 1,
"days": [
"M",
"Th"
],
"occurrences": 8
} {
"client": "Client D",
"workout": "Lower body A",
"rule": "Weekly · M, Th · 8×",
"first": "2026-11-23",
"last": "2026-12-17"
} History shows each earlier session: date, what you prescribed, every logged set and the client's notes. The completed view shows completion date, exercises, total sets logged and new comments, with weight × reps per set next to your prescription.
MCP callcoach_catalyst_read → view_workout_progress
REST endpointGET https://cotlet.dev/api/v1/coach-catalyst/workout-progress/view
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name or email, as list_clients returns it. |
| exercise string | string | For the History tab: every earlier session of this exercise. |
| workout_date string | string | ISO date, for the completed view of that day's workout. |
{
"client": "client"
} {
"client": "Client A",
"exercise": "Back squat",
"history": [
{
"date": "2026-11-13",
"prescribed": "4 × 6 @RPE 7",
"logged": [
"100×6",
"100×6",
"105×5",
"105×5"
]
},
{
"date": "2026-11-10",
"prescribed": "4 × 6 @RPE 7",
"logged": [
"97.5×6",
"97.5×6",
"100×6",
"100×5"
]
}
]
} Returns a link to the PDF for you to print or send yourself; the agent does not send it to the client.
MCP callcoach_catalyst_read → print_workout
REST endpointGET https://cotlet.dev/api/v1/coach-catalyst/workouts/print
| Name | Type | Description |
|---|---|---|
| client string required | string | Client name or email, as list_clients returns it. |
| workout_date string required | string | ISO date of the workout. |
{
"client": "client",
"workout_date": "workout date"
} {
"client": "Client D",
"workout": "Lower body A",
"pdf": "lower-body-a-2026-11-23.pdf"
} Folders of PNG, JPG, GIF and PDF files, who can see each folder, and communities for groups and challenges.
Clients see resources in the Resources tab of their app, but only in folders they are added to, so creating a folder or adding a file reaches no one and runs without asking. A file needs a folder first.
MCP callcoach_catalyst_write → manage_resource_folders
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/resource-folders/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | `list`, `create_folder` or `upload`. `list` only reads. |
| folder string | string | Folder name. |
| file_url string | string | For `upload`: a link the Cloud Browser can download the file from, up to 25 MB. |
{
"action": "action"
} {
"folder": "Meal guides",
"files": [
"Grocery list.pdf",
"Protein swaps.png"
]
} Every account has one default community that all active clients and coaches join. Custom communities need the Coach Pro plan. Members see a new community at once, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → manage_communities
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/communities/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | `list` or `create`. `list` only reads. |
| name string | string | For `create`. |
| members array | array | For `create`: clients and coaches to add. |
{
"action": "action"
} {
"community": "January challenge",
"members": 14,
"created": true
} Paid and free products with discount links, Stripe revenue and payouts, the welcome messages and compliance reports.
Paid products take payment through Stripe; free products need no Stripe and assign the client straight away. A buyer can only get a discount through a link that already carries the code, and a $0 or 100% off one-time payment does not work with Stripe. A product reaches buyers, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → manage_products
REST endpointPOST https://cotlet.dev/api/v1/coach-catalyst/products/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | `list`, `create` or `share_link`. `list` only reads. |
| product string | string | Product name. |
| fields object | object | For `create`: description, cover photo, price or free, and what a buyer gets (program and start date, community, group, coach). |
| discount object | object | For `create`: a one-word code and an amount in dollars or percent. |
| with_discount string | string | For `share_link`: the discount code to build into the link. |
{
"action": "action"
} {
"product": "12-Week Strength",
"price_usd": 249,
"discount": {
"code": "NEWYEAR20",
"percent": 20
},
"share_link": "https://example.com/p/12-week-strength?code=NEWYEAR20"
} Reads the Payments dashboard, the product buyer lists, a client's Purchases tab and the Payouts tab: the balance Stripe owes you and the payout history. Refunds and cancelling subscriptions are not part of this tool.
MCP callcoach_catalyst_read → review_payments
REST endpointGET https://cotlet.dev/api/v1/coach-catalyst/payments/review
| Name | Type | Description |
|---|---|---|
| product string | string | Only buyers of this product. |
| client string | string | Only this client's purchases. |
{
"revenue_month_usd": 2490,
"purchases": [
{
"client": "Client D",
"product": "12-Week Strength",
"amount_usd": 199.2,
"date": "2026-11-14"
}
],
"payout_balance_usd": 640
} Found under Settings > Notifications. The welcome message invites the client to set up a login and download the MyCoach app or your branded app. Some parts of the message are required for that to work, so the agent keeps them and changes only the wording around them. Every new client reads it, so changes wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callcoach_catalyst_write → edit_welcome_messages
REST endpointPATCH https://cotlet.dev/api/v1/coach-catalyst/welcome-messages
| Name | Type | Description |
|---|---|---|
| channel string required | string | `email` or `text`. |
| content string | string | New wording. Leave empty to read. |
{
"channel": "channel"
} {
"channel": "email",
"subject": "Welcome to Example Coaching",
"saved": true
} Coach Catalyst suggests reports to show what your programs achieve, for example results at different compliance levels. Download As File gives a CSV.
MCP callcoach_catalyst_read → view_reports
REST endpointGET https://cotlet.dev/api/v1/coach-catalyst/reports/view
| Name | Type | Description |
|---|---|---|
| coaches array | array | One, several or all coaches. |
| from string | string | ISO start date. |
| to string | string | ISO end date. |
| clients array | array | Chosen clients or a group. Leave empty for all. |
| metrics array required | array | One or more metrics, for example compliance. |
{
"metrics": "metrics"
} {
"from": "2026-10-01",
"to": "2026-10-31",
"metric": "compliance",
"rows": [
{
"client": "Client A",
"compliance": 94
},
{
"client": "Client B",
"compliance": 72
}
]
} Your signed-in Coach Catalyst browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 25 Coach Catalyst tools. The session cookie stays in the Cloud Browser.
The clients, messages, programs and payments your coach account can open, and nothing more.
Your Stripe connection, refunds and subscriptions, your Coach Catalyst plan, permanent client deletion and your Zapier and app integrations.
You sign in again yourself, in the same Cloud Browser.
Disable Coach Catalyst for agents, reset the browser, or change your Coach Catalyst password.
Cotlet never sees or stores your password: you sign in to Coach Catalyst yourself, and the agent only uses the session that sign-in leaves. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Journey element on the wrong day | Move it back with move_journey_element |
| Program started by mistake | Stop it with stop_program; the client stops getting its lessons |
| Folder shared with the wrong client | Remove them with share_resource_folder |
| Message sent | Already with the client: follow up in a new message |
14 of the 19 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 5 that change only your own library or labels, tags, lessons, exercises, workout templates and resource folders, run at once, as do the 6 read tools.
{
"name": "schedule_repeating_workout",
"arguments": {
"client": "Client D",
"workout": "Lower body A",
"start_date": "2026-11-23",
"every_weeks": 1,
"days": [
"M",
"Th"
],
"occurrences": 8
}
} curl -X POST https://cotlet.dev/api/v1/coach-catalyst/repeating-workout/schedule \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"client":"Client D","workout":"Lower body A","start_date":"2026-11-23","every_weeks":1,"days":["M","Th"],"occurrences":8}' {
"client": "Client D",
"workout": "Lower body A",
"rule": "Weekly · M, Th · 8×",
"first": "2026-11-23",
"last": "2026-12-17"
} The example repeats Lower body A on Mondays and Thursdays from 23 November: eight occurrences end on 17 December. A cron job or n8n flow can make the same call over REST at /api/v1/coach-catalyst with the same key and price, in JSON. Failed calls are free.
About $19 a monthfor a solo coach with about 40 active clients, 3,220 credits. Your Coach Catalyst plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning inbox read and two replies | 3 × 30 | 900 |
| Weekly low-compliance list and six check-ins | 7 × 4 | 280 |
| Weekly check-in forms plus five training histories | 6 × 4 | 240 |
| New client: add, program, resources | 3 × 4 | 120 |
| Workout template and repeat schedule | 2 × 8 | 160 |
| Monthly report and payments | 2 × 1 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 172 calls | 3,220 |
The smallest pack, 5,000 credits for $29, covers this month. A coaching team with several coaches sends more messages and uses more calls.
Credit packs are one-time purchases, not a subscription. The month above is built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| Coach Catalyst Zapier app | The official automation route; Zapier can add clients automatically. | Fixed triggers and actions; no inbox, programs or workouts from a chat. |
| Growth Catalyst CRM and Payments | Coach Catalyst's own ways to add clients as they sign up or buy. | Bring clients in; the coaching work after that is yours. |
| By hand | The desktop app and the coach side of the mobile app. | One client and one screen at a time. |
If Zapier already adds your clients, keep it. Cotlet fits when you want ChatGPT, Claude or a script to work inside Coach Catalyst on the rest, from your own login, with nothing to host.
Take Group sp. z o.o. is the company behind Cotlet, a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). For questions about the Coach Catalyst tools, write to contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=coach-catalyst, turn on Coach Catalyst under Integrations in the console and sign in at https://app.coachcatalyst.com/auth/sign_in in your Cloud Browser. Then connect your AI agent and ask it who is waiting in your inbox. The trial needs no card.
Coach Catalyst publishes no public API: no developer documentation, API key page or API plan was found on its website or Help Center (checked 16 Nov 2026). Its official automation route is a Zapier app, and no Coach Catalyst MCP server or official ChatGPT or Claude connector was found. Cotlet does not need one: it works in your own signed-in Coach Catalyst account.
No. Keep Zapier if it already adds clients from your forms or CRM. Cotlet covers the work Zapier does not reach, such as reading the inbox, assigning programs or building workouts, and can run next to it.
The tools work on your current plan. Custom communities need the Coach Pro plan, as the Help Center article All About Communities says; the Coach plan has one community.
Messages go out from your coach account, the same as when you send them, and only after you approve each one unless you switch confirmation off for send_client_message.
Only in how it is called. Both carry the same 25 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Coach Catalyst.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy