Workflow · Bookings and scheduling
Booking confirmation and reminder
Two workflows for any table of bookings, appointments or reservations. The confirmation goes out the moment the row is created; the reminder runs every hour and emails everyone whose booking starts within the next 24 hours, once. Cancelled and declined bookings are skipped. It adds one field, reminder_sent_at, so nobody is reminded twice.
use_template { slug: "booking-confirmation-and-reminder" } adds
- Fields
- ‹booking›.reminder_sent_at
- Workflows
- booking-confirmation, booking-reminder
What it adds to your app
Confirmation email on every new booking. Hourly reminder for bookings in the next 24 hours. A reminder_sent_at field so nobody gets two.
Fields added to your tables
‹booking›.reminder_sent_at
Workflows
booking-confirmationEmail a confirmation for each new ‹booking›. On ‹booking› createdbooking-reminderRemind people the day before their ‹booking›. On schedule hourly over ‹booking›
Where it attaches
Params point the template at your own 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 |
|---|---|---|
booking | The table of bookings, appointments or reservations. Optional. | booking |
starts_field | The date or timestamp field holding when the booking starts. Optional. | starts_at |
customer_ref | The ref field on the booking that points at the person who made it. Optional. | customer_id |
email_field | The email field on the person's table. Optional. | email |
tz | The IANA time zone booking times are shown in, like Europe/London or America/New_York. Optional. | Europe/London |
Use with your coding agent
- Connect the Appbricx MCP server to Claude Code, Cursor or any MCP client (quickstart).
- Paste the prompt. The agent reads the template, previews the merge with dry_run and shows you the diff.
- It applies to dev. Check it, then deploy when you are happy.
Add the Booking confirmation and reminder template (slug "booking-confirmation-and-reminder") 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 (booking: bookings table; starts_field: when it starts; customer_ref: who booked; email_field: their email field; tz: time zone).{
"tool": "use_template",
"arguments": {
"slug": "booking-confirmation-and-reminder",
"project_id": "<your project id>",
"params": {
"booking": "booking",
"starts_field": "starts_at",
"customer_ref": "customer_id",
"email_field": "email",
"tz": "Europe/London"
},
"dry_run": true
}
}appbricx templates use booking-confirmation-and-reminder --param booking=booking --param starts_field=starts_at --param customer_ref=customer_id --param email_field=email --param tz=Europe/London --dry-runGoes well with
Studio Bookings
App. Class booking for a yoga and pilates studio: members book in two taps, instructors run the schedule.
memberinstructorsessionbookingClassScheduleBooking calendar
Block. Bookable time slots with capacity, a day picker, my bookings with cancel, and rules that stop double-booking.
slotreservationSlotPickerMyReservationsreservation-countWelcome email
Workflow. Emails every new person a short, friendly welcome the moment they sign up.
welcome-email