Skip to main content

Booking Changed Trigger

The Booking Changed trigger starts a workflow when a booking is rescheduled or amended in your CaptainBook system.

Jerome Bajou avatar
Written by Jerome Bajou
Updated this week

Overview

The Booking Changed trigger starts a workflow when a booking is rescheduled or amended in your CaptainBook system.

When It Triggers

  • Booking dates or times are changed

  • Booking details are modified (quantity, product, etc.)

  • Booking is rescheduled

  • Any amendment is made to an existing confirmed booking

Use Cases

  • Send change confirmation emails

  • Notify customers about modifications

  • Update external calendars

  • Notify staff about changes

  • Recalculate pricing

  • Update partner systems


Configuration

This trigger requires no additional configuration. It automatically triggers when any confirmed booking is modified.


Available Data

When this trigger fires, it provides a booking object with the updated booking information.

Booking Object Structure

The booking object includes all standard booking fields with the latest values:

  • Updated dates and times

  • Modified quantities

  • Changed product information

  • Updated pricing

  • All customer and booking details

Accessing Booking Data

{booking.id} 
{booking.updated_at}
{booking.gross_price}
{booking.quantity}

Example Workflows

1. Send Change Confirmation

Workflow Steps:

  1. Trigger: Booking Changed

  2. Action: Send Notification

    • To: {booking.customer.email}

    • Subject: "Your Booking Has Been Updated"

    • Body: Include updated booking details

2. Update External Calendar

Workflow Steps:

  1. Trigger: Booking Changed

  2. Action: Send Webhook

    • URL: External calendar system

    • Payload: Updated booking details

3. Notify Staff

Workflow Steps:

  1. Trigger: Booking Changed

  2. Condition: If {booking.quantity} changed

  3. Action (True): Send Notification to operations team


Testing

When testing this trigger:

  1. Select a confirmed booking from your system

  2. The workflow will use that booking's current data

  3. Review execution logs to see booking information

Test Data

The trigger provides access to the last 20 confirmed bookings for testing.


Best Practices

  1. Compare changes - Use conditions to detect specific types of changes

  2. Update all systems - Ensure external systems are synchronized

  3. Notify promptly - Send change confirmations quickly

  4. Handle availability - Release old slots and reserve new ones

  5. Track modifications - Log changes for audit purposes


Related Documentation

Did this answer your question?