Skip to main content

Remove Resource Block Action

The Remove Resource Block action removes a resource block (user event) by its ID. This action deletes a previously created block that prevents a resource from being available during a specific time period.

Jerome Bajou avatar
Written by Jerome Bajou
Updated this week

Overview

The Remove Resource Block action removes a resource block (user event) by its ID. This action deletes a previously created block that prevents a resource from being available during a specific time period.


Configuration

User Event ID (Required)

The ID of the user event (resource block) to remove. Must be a valid user event ID that:

  • Has event_id set to blocked_dates

  • Belongs to a user in the same business unit as the workflow

Supports variables from the workflow context.

Example:

{user_event.id}

or

123

Output

This action does not return any output context. The resource block is permanently deleted from the system.


Examples

1. Remove Block from Context Variable

User Event ID: {user_event.id}

This removes the block referenced by a user event from a previous workflow step.

2. Remove Block by Direct ID

User Event ID: 456

This removes the block with ID 456 (if it belongs to a user in the same business unit).


Validation

The action validates:

  • User Event ID is required and not empty

  • User event exists in the system

  • User event has event_id set to blocked_dates

  • User owning the event belongs to the same business unit as the workflow

If any validation fails, an InvalidArgumentException is thrown.


Best Practices

  1. Verify ownership - Ensure the block belongs to a user in your business unit before attempting to remove

  2. Use variables - Reference blocks from previous workflow steps using context variables

  3. Handle errors - Set up error notifications for cases where blocks cannot be found

  4. Check before removing - Consider using the Get Resource Block action first to verify the block exists

  5. Business unit scoping - Remember that blocks are automatically scoped to your workflow's business unit


Related Documentation

Did this answer your question?