Integrations
Send events from outside tools into the app and see what arrived.
How events arrive
Each workspace has its own secure address for three kinds of events: workouts, purchases and CRM changes. Your automation tool posts to that address. The app stores each event and applies it the next time you open the app, or when you press Process pending.
The Integrations screen
| Part | What it does |
|---|---|
| Webhook endpoints | The addresses and keys for your workspace. Copy copies one. Rotate key replaces the key. |
| Send test event | Sends a sample event so you can see it arrive. |
| Process pending | Applies waiting events now. |
| Inbox | Every event with its status: pending, applied or rejected. |
Why an event is rejected
- A workout event has no client email or CRM id, so the app cannot tell whose it is.
- The key does not match your workspace's key.
- A cancelled or past-due purchase arrives for someone who is not yet a client.
Rejected events are not retried. Fix the cause and send a new event.
Rotating a key stops every automation that uses the old key until you update it.
Was this page helpful?