Skip to main content

Get Resource Action

The Get Resource action retrieves a resource by ID and adds it to the workflow context. Use this to access resource information for availability checks, booking assignments, or notifications.

Jerome Bajou avatar
Written by Jerome Bajou
Updated today

Overview

The Get Resource action retrieves a resource by ID and adds it to the workflow context. Use this to access resource information for availability checks, booking assignments, or notifications.


Configuration

Resource ID (Required)

The ID of the resource to retrieve. Supports variables.

Examples:

{resource.id} 
{booking.resource_id}
{webhook_payload.resource_id}

Output

Adds a resource object to the workflow context with resource details:

  • Resource ID

  • User ID (if resource is assigned to a user)

  • Name

  • Type

  • Category

  • Capacity

  • Rating

  • Rating number

  • Created/updated timestamps

Accessing Resource Data

After this action, you can access:

{resource.id} 
{resource.name}
{resource.type}
{resource.category}
{resource.capacity}
{resource.user_id}

Use Cases

  • Retrieve resource details for availability checks

  • Get resource information for booking assignments

  • Access resource data for notifications

  • Load resource for processing in workflows


Examples

1. From Booking

Workflow:

  1. Booking Confirmed trigger

  2. Get Resource ({booking.resource_id})

  3. Determine if Available next day (check resource availability)

  4. Notify customer of tentative slots on the next day

2. From Webhook

Workflow:

  1. Webhook trigger

  2. Get Resource ({payload.resource_id})

  3. Send Notification (include resource details)

3. Direct Resource Lookup

Workflow:

  1. Scheduled Time trigger

  2. Get Resource (123)

  3. Check availability and send notifications


Best Practices

  1. Verify ID exists - Check resource ID before using

  2. Handle not found - Set up error handling for missing resources

  3. Use in conditions - Check resource properties before actions

  4. Cache when possible - Avoid repeated lookups in same workflow


Related Documentation

Did this answer your question?