Overview
The Auxiliary Resource Detached from Booking trigger starts a workflow when an auxiliary resource is detached from a booking in your CaptainBook system.
When It Triggers
An auxiliary resource is detached from a booking
Only triggers for resources with the "auxiliary" category
Triggers immediately upon detachment
Works for both automatic and manual auxiliary resource removals
Use Cases
Notify auxiliary resource users about removal
Update external systems with auxiliary resource removals
Release auxiliary resource availability
Update availability calendars
Send notifications to customers about changes
Track auxiliary resource utilization changes
Create reassignment workflows for auxiliary resources
Log auxiliary resource detachment for audit purposes
Handle capacity adjustments after removal
Configuration
This trigger requires no additional configuration. It automatically triggers when any auxiliary resource is detached from a booking.
Available Data
When this trigger fires, it provides booking_id and resource_id that you can use to access booking and auxiliary resource information in your workflow actions.
Context Variables
The trigger provides the following context variables:
booking_id- The ID of the booking that the auxiliary resource was detached fromresource_id- The ID of the auxiliary resource that was detached
Accessing Context Data
{booking_id}
{resource_id}Using Context in Actions
You can use these IDs to:
Query booking details using
{booking_id}Query auxiliary resource details using
{resource_id}Access booking customer information
Access auxiliary resource user information
Get resource type and capacity information
Example Workflows
1. Notify Auxiliary Resource User
Workflow Steps:
Trigger: Auxiliary Resource Detached from Booking
Action: Send Notification
To: Auxiliary resource user email (query using
{resource_id})Subject: "Auxiliary Resource Assignment Removed"
Body: Include booking details and reason for removal
2. Release Availability
Workflow Steps:
Trigger: Auxiliary Resource Detached from Booking
Action: Update Availability
Release auxiliary resource slots for the booking period
Make auxiliary resource available for other bookings
3. Customer Notification
Workflow Steps:
Trigger: Auxiliary Resource Detached from Booking
Action: Send Notification
To: Booking customer email (query using
{booking_id})Subject: "Booking Update - Auxiliary Resource Change"
Body: Inform customer about auxiliary resource change and next steps
4. Audit Logging
Workflow Steps:
Trigger: Auxiliary Resource Detached from Booking
Action: Send Webhook
Include
{booking_id}and{resource_id}in payloadLog detachment to external audit system
Action: Update Booking (add note about auxiliary resource removal)
5. Capacity Adjustment
Workflow Steps:
Trigger: Auxiliary Resource Detached from Booking
Condition: Check if booking still meets capacity requirements
Action (False): Send Alert to operations team
Action: Update booking capacity calculations
Testing
When testing this trigger:
Select a booking that has auxiliary resources attached
Select a specific auxiliary resource from that booking
The workflow will use that booking and auxiliary resource data
Review execution logs to verify auxiliary resource and booking information
Test Data
The trigger provides access to the last 20 bookings with auxiliary resources attached for testing. You can select any booking and then choose from its attached auxiliary resources.
Best Practices
Notify promptly - Send notifications immediately after detachment
Release availability - Update auxiliary resource availability calendars
Update customers - Inform customers about auxiliary resource changes
Maintain audit trail - Log all auxiliary resource detachments
Handle reassignments - Consider workflows for automatic reassignment of auxiliary resources
Sync external systems - Update external calendars and systems
Check capacity - Verify booking still meets capacity requirements after removal
Handle automatic removals - Ensure workflows work with automatic auxiliary resource removal features