Nook

What's inside

Stays grid with photo carousels. Booking panel with price breakdown. Host listings, requests and earnings.

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. Booking requested → notify host and hold the dates

   When a row changes: booking created. Then: Notify, then Create booked_range.

2. Booking confirmed → notify guest

   When a row changes: booking updated, when status is confirmed. Then: Notify.

3. Booking declined → notify guest, free the dates

   When a row changes: booking updated, when status is declined. Then: Notify, then Look up booked_range, then Update booked_range.

4. Daily: complete bookings whose check-out has passed

   On a schedule: schedule daily 06:00 over booking. Then: Look up booking, then Update booking.

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 Nook template (slug "nook") with use_template. Call it "My Nook", then sign in as each role, verify it and tell me what to change first.

{
  "tool": "use_template",
  "arguments": {
    "slug": "nook",
    "name": "My Nook"
  }
}

appbricx templates use nook --name "My Nook"