Skip to main content

Get Product Action

The Get Product action retrieves a product by ID and adds it to the workflow context.

Jerome Bajou avatar
Written by Jerome Bajou
Updated over a week ago

Overview

The Get Product action retrieves a product by ID and adds it to the workflow context.


Configuration

Product ID (Required)

The ID of the product to retrieve. Supports variables.

Examples:

{product.id} 
{schedule.product_id}
{webhook_payload.product_id}

Output

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

  • Basic information (id, uuid, title, product_code)

  • Schedule type and configuration

  • Pricing information (from_price, tier pricing settings)

  • Product settings (active, private, displayable, can_be_sold)

  • Content (description, instructions, requirements, inclusions, exclusions)

  • Cancellation policy

  • Notification settings

  • Localization (locale, timezone)

  • Tax and delivery information

Accessing Product Data

After this action, you can access:

{product.id} 
{product.uuid}
{product.title}
{product.product_code}
{product.schedule_type}
{product.description}
{product.is_active}
{product.is_private}
{product.is_priced_per_person}
{product.is_tier_priced}
{product.from_price}
{product.from_price_label}
{product.capacity}
{product.rating}
{product.rating_number}
{product.cancellation_policy}
{product.cancellation_policy_link}
{product.instructions}
{product.requirements}
{product.inclusions}
{product.exclusions}
{product.locale}
{product.timezone}
{product.vat_rate}
{product.delivery_method}
{product.redemption_method}

Use Cases

  • Retrieve product details from booking

  • Get product information from schedule

  • Access product for notifications

  • Load product for pricing calculations

  • Validate product settings

  • Access product content for communications


Examples

1. From Schedule

Workflow:

  1. Booking Confirmed trigger

  2. Get Schedule ({booking.availabilities.0.bookable_id})

  3. Get Product ({schedule.product_id})

  4. Send notification with product title and description

2. From Booking

Workflow:

  1. Booking Changed trigger

  2. Get Product ({booking.availabilities.0.bookable.product_id})

  3. Check if product is active ({product.is_active})

  4. Validate cancellation policy if required

3. Product Information Email

Workflow:

  1. Booking Confirmed trigger

  2. Get Product ({booking.availabilities.0.bookable.product_id})

  3. Send notification with:

    • Product title: {product.title}

    • Instructions: {product.instructions}

    • Requirements: {product.requirements}

    • Inclusions: {product.inclusions}

4. Pricing Information

Workflow:

  1. Webhook trigger

  2. Get Product ({payload.product_id})

  3. Check pricing type ({product.is_tier_priced}, {product.is_priced_per_person})

  4. Calculate pricing based on product settings


Best Practices

  1. Verify ID exists - Check product ID before using

  2. Handle not found - Set up error handling for invalid product IDs

  3. Use with schedule - Combine with Get Schedule action for complete schedule information

  4. Check active status - Validate {product.is_active} before processing bookings

  5. Respect settings - Check {product.can_be_sold} and {product.displayable} flags


Related Documentation

Did this answer your question?