Skip to main content

Get Booking Action

The Get Booking action retrieves a booking by ID and adds it to the workflow context. Use this to access booking details when you only have a booking ID.

Jerome Bajou avatar
Written by Jerome Bajou
Updated yesterday

Overview

The Get Booking action retrieves a booking by ID and adds it to the workflow context. Use this to access booking details when you only have a booking ID.


Configuration

Booking ID (Required)

The ID of the booking to retrieve. Supports variables.

Examples:

{booking.id} 
{transaction.booking_id}
{webhook_payload.booking_id}
12345

Output

Adds a booking object to the workflow context with all booking details:

  • Booking ID, dates, pricing

  • Customer information

  • Product details

  • Status, notes, comments

  • All standard booking fields

Accessing Booking Data

After this action, you can access:

{booking.id} 
{booking.customer_id}
{booking.gross_price}
{booking.confirmed_at}

Use Cases

  • Retrieve booking from transaction

  • Get booking details from webhook data

  • Access booking from external system reference

  • Load booking for processing


Examples

1. From Transaction

Workflow:

  1. Booking Transaction Processed trigger

  2. Get Booking ({transaction.booking_id})

  3. Send Notification (use booking details)

2. From Webhook

Workflow:

  1. Webhook trigger

  2. Get Booking ({payload.booking_id})

  3. Update Booking (with webhook data)

3. Process Booking

Workflow:

  1. Scheduled Time trigger

  2. Find Bookings (get booking IDs)

  3. Loop

  4. Get Booking ({current_item.id})

  5. Process each booking


Best Practices

  1. Verify ID exists - Check booking ID before using

  2. Handle not found - Set up error handling

  3. Use in loops - Get booking details for each item

  4. Cache when possible - Avoid multiple Get Booking calls


Related Documentation

Did this answer your question?