Overview
The Auxiliary Resource Attached to Booking trigger starts a workflow when an auxiliary resource is attached to a booking in your CaptainBook system.
When It Triggers
An auxiliary resource is attached to a booking
Only triggers for resources with the "auxiliary" category
Triggers immediately upon attachment
Works for automatically and manually assigned auxiliary resources
Use Cases
Send notifications to auxiliary resource users
Update external systems with auxiliary resource assignments
Notify customers about additional resources
Track auxiliary resource utilization
Generate auxiliary resource assignment reports
Update availability calendars
Send welcome messages to auxiliary resources
Create task assignments for auxiliary resources
Handle automatic auxiliary resource assignments
Configuration
This trigger requires no additional configuration. It automatically triggers when any auxiliary resource is attached to 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 attached toresource_id- The ID of the auxiliary resource that was attached
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 Attached to Booking
Action: Send Notification
To: Auxiliary resource user email (query using
{resource_id})Subject: "New Auxiliary Resource Assignment"
Body: Include booking details, customer information, and capacity requirements
2. Update External System
Workflow Steps:
Trigger: Auxiliary Resource Attached to Booking
Action: Send Webhook
Include
{booking_id}and{resource_id}in payloadNotify external system of auxiliary resource assignment
Include capacity and scheduling information
3. Customer Notification
Workflow Steps:
Trigger: Auxiliary Resource Attached to Booking
Action: Send Notification
To: Booking customer email (query using
{booking_id})Subject: "Additional Resource Assigned"
Body: Include auxiliary resource details and contact information
4. Automatic Assignment Tracking
Workflow Steps:
Trigger: Auxiliary Resource Attached to Booking
Condition: Check if assignment was automatic
Action: Update Booking (add note about auxiliary resource assignment)
Action: Log to external analytics system
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
Verify auxiliary resource availability - Check resource schedule before assignment
Notify promptly - Send notifications immediately after attachment
Track assignments - Log auxiliary resource assignments for analytics
Update calendars - Sync auxiliary resource assignments with external calendars
Handle capacity - Consider capacity requirements when assigning auxiliary resources
Maintain records - Keep audit trail of auxiliary resource assignments
Support automatic assignment - Ensure workflows work with automatic auxiliary resource assignment features