Workflows
Workflows run when a booking changes state. Each one sends the right message, creates the right task or asks for the right approval at the right moment.
| When a booking is… | You might… |
|---|---|
| Confirmed | Send the confirmation, add it to the CRM, notify the host |
| Changed | Tell everyone affected and update linked records |
| Cancelled | Release the resources and invite the next person on the waitlist |
| Attended | Send a follow-up, create a task, schedule the next session |
Note
Workflows react to scheduling state, so they stay correct when bookings move. You never have to remember to send the update yourself.
Payments
Payment is part of the booking, not a separate process. Each booking shows whether payment is needed and where it stands, and registration and payment move forward together.
| Payment setting | Example |
|---|---|
| Not required | A free strategy call |
| Deposit requested | A design review held with a deposit |
| Paid | A workshop seat confirmed after payment |
| Required | A program seat that needs payment to be confirmed |
Integrations
TimeSlotX connects the systems scheduling depends on: calendars, CRM, video, payments, messaging and data. Each integration is an input or an output of the same scheduling flow. See Developers for APIs, webhooks and MCP.