Booking calendar

What it adds to your app

Tables slot and reservation. SlotPicker and MyReservations components with their pages. Staff week calendar and reservations list. Workflows that keep places left up to date.

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 booked places on the time slot

   When a row changes: reservation created. Then: Look up slot, then Update slot.

2. Cancel a booking when its person asks

   When a row changes: reservation updated, when cancel_request is requested. Then: Update reservation.

3. Free the places when a booking is cancelled

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

4. Give each time slot the organisation of what is booked

   When a row changes: slot created. Then: Look up ‹attach_to›, then Update slot.

Set it up

It merges into the contract of an app you already have. Nothing is overwritten: a name you already use is refused until you pass a prefix.

1. Pick the project

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

2. Point it at your tables and roles

   Leave out the ones with defaults; a wrong one is refused with the options your app has.

   Param	What it is	Example
   attach_to	The table of things people book time with (rooms, coaches, courts, services).	room
   booker_role	The role whose people make bookings (their own table is the booker). Optional.	member
   org_field	Optional: the ref on that table naming its organisation (from organisations-and-teams). Time slots then belong to that organisation and only its members see and book them. Optional.	organisation_id

3. Preview, then apply to dev

   A dry run shows the diff and the check report; applying it changes your dev environment only.

4. Deploy

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

Use it with your coding agent

The agent reads the template, runs a dry run, shows you the diff and applies it.

Add the Booking calendar template (slug "booking-calendar") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (attach_to: what is booked; booker_role: who books; org_field: organisation (optional)).

{
  "tool": "use_template",
  "arguments": {
    "slug": "booking-calendar",
    "project_id": "<your project id>",
    "params": {
      "attach_to": "room",
      "booker_role": "member",
      "org_field": "organisation_id"
    },
    "dry_run": true
  }
}

appbricx templates use booking-calendar --param attach_to=room --param booker_role=member --param org_field=organisation_id --dry-run