Skip to main content

Determine if Resource Available Action

The Determine if Available action checks whether a resource is available during a specified time period. Use this to verify resource availability before creating bookings or scheduling activities.

Jerome Bajou avatar
Written by Jerome Bajou
Updated today

Overview

The Determine if Available action checks whether a resource is available during a specified time period. Use this to verify resource availability before creating bookings or scheduling activities.


Configuration

Resource ID (Required)

The ID of the resource to check. Supports variables.

Start (Required)

The start date and time for the availability check. Supports variables and relative times.

Formats:

  • ISO 8601: 2024-01-15T10:00:00

  • With timezone: 2024-01-15T10:00:00+02:00

  • Relative: +1 day, tomorrow 10:00

End (Required)

The end date and time for the availability check. Supports variables and relative times.

Formats:

  • ISO 8601: 2024-01-15T14:00:00

  • With timezone: 2024-01-15T14:00:00+02:00

  • Relative: +2 hours, +1 day

Timezone (Optional)

Timezone for date/time parsing. Defaults to workspace timezone if not specified. Supports variables.

Examples:

  • America/New_York

  • Europe/London

  • UTC


Output

Returns an is_available boolean value indicating whether the resource is available during the specified time period.

Accessing Result

After this action, you can access:

{is_available}

Note: Resources without an associated user are always considered available.


Examples

1. Check Availability for Specific Time

Resource ID: {resource.id} 
Start: 2024-06-15T10:00:00
End: 2024-06-15T14:00:00
Timezone: America/New_York

2. Check Availability from Booking

Resource ID: {booking.resource_id} 
Start: {booking.start}
End: {booking.end}

3. Check Availability for Tomorrow

Resource ID: {resource.id} 
Start: tomorrow 09:00
End: tomorrow 17:00

4. Check Availability with Relative Times

Resource ID: {resource.id} 
Start: +1 day 10:00
End: +1 day 14:00

How It Works

  1. Parses start and end times (handles timezone conversion)

  2. Finds the resource and its associated user

  3. Checks if the user is free during the specified period

  4. Returns true if available, false if conflicts exist

Note: The action checks against user events (bookings, calendar events, etc.) to determine availability.


Best Practices

  1. Verify resource exists - Check resource ID before checking availability

  2. Use correct timezone - Specify timezone if different from your workspace's default

  3. Handle time parsing - Use ISO 8601 format for reliability

  4. Check before booking - Always verify availability before creating bookings

  5. Consider buffer time - Account for setup/cleanup time if needed


Related Documentation

Did this answer your question?