Studio Bookings

What's inside

Weekly schedule with one-tap booking. My classes with cancel. Instructor desk with rosters, check-in and a bookings chart.

How its workflows run

Each one is a server workflow in your project: it runs on its trigger, with retries, and its runs show in the builder's log.

1. Count the mat and tell instructors

   When a row changes: booking created. Then: Look up session, then Update session, then Notify.

2. Free the mat when a booking is cancelled

   When a row changes: booking updated, when status is cancelled. Then: Look up session, then Update session.

3. Morning bookings digest

   On a schedule: schedule daily 07:00 over booking. Then: Notify instructor.

4. Weather for a garden class

   When the app calls it: server function (member, instructor). Then: Look up session.

Set it up

It starts a new project, with its data, roles and sign-in ready.

1. Start the project

   Use the button above, or ask your coding agent with the Appbricx MCP server connected (quickstart).

2. Sign in as each role

   The demo logins open each role's home. Change what you like in plain words or in the contract.

3. Deploy

   When dev looks right, deploy. Production gets a snapshot first, so you can roll back.

Use it with your coding agent

The agent creates the project, builds it and signs in as each role.

Start a new Appbricx project from the Studio Bookings template (slug "studio-bookings") with use_template. Call it "My Studio Bookings", then sign in as each role, verify it and tell me what to change first.

{
  "tool": "use_template",
  "arguments": {
    "slug": "studio-bookings",
    "name": "My Studio Bookings"
  }
}

appbricx templates use studio-bookings --name "My Studio Bookings"