A new lead can land in your own follow-up sheet, a cancellation request can send you a text so you can call the client the same day, and a new signup can be added to your email list.
In other words Zapier lets you connect Coachway to many other tools, so that something happening in Coachway can automatically start an action somewhere else.
⚠️ Coachway's Zapier integration is triggers only.
Zapier can react to things happening in Coachway, but it cannot send anything back into Coachway. See "What the integration cannot do" below before you plan a workflow around it.
Before you start
You need permission to manage the account. If you are a team member without account admin rights, you will not see the Integrations page, and your account owner will need to set the connection up.
Connecting your account
Go to Settings → Account → Integrations.
From there you can create your API key and open the invitation link to the Coachway Zapier app.
💡 Your API key is shown once only. Copy it and store it somewhere safe when it appears. If you lose it, you will need to create a new one.
Coachway's Zapier app is private, which means it does not appear if you search the public Zapier directory. You can only reach it through the invitation link on the Integrations page.
Available triggers
There are nine events you can subscribe to:
New lead created
Lead changes status — you can filter on a specific status such as Won or Lost, or leave the field empty to catch every status change
Lead accepts an offer
New client created
Client logs into the app for the first time
Purchase completed
Subscription started
Client requests cancellation
Subscription ended
On status changes, both the new and the previous status are included. That means you can build automations that react to the direction of a change, for example only when a lead moves from Offer sent to Won, rather than on every status change.
What the integration cannot do
The integration is one-way. Zapier can be told what happened in Coachway, but it cannot create or change anything in your account. Specifically, none of the following are possible:
Creating clients
Reading onboarding form responses
Creating or assigning meal plans
Uploading files, PDFs or progress photos
Sending messages to clients
There is also no public REST API and no developer documentation.
Your API key authorises Zapier to subscribe to the nine events above and nothing else, so it cannot be used from Make, n8n, or your own HTTP requests.