Booking confirmation and 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.

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. Email a confirmation for each new ‹booking›

   When a row changes: ‹booking› created. Then: Look up ‹customer_ref›, then Send email.

2. Remind people the day before their ‹booking›

   On a schedule: schedule hourly over ‹booking›. Then: Look up ‹booking›, then Send email, then Update ‹booking›.

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
   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

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 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-run