Skip to main content

Documents Signed Complete Trigger

The Documents Signed Complete trigger starts a workflow when all required documents for a booking have been signed in your CaptainBook system.

Jerome Bajou avatar
Written by Jerome Bajou
Updated this week

Overview

The Documents Signed Complete trigger starts a workflow when all required documents for a booking have been signed in your CaptainBook system.

When It Triggers

  • All required documents for a booking are signed

  • Final signature is completed

  • Document signing process is fully completed

Use Cases

  • Send completion confirmation

  • Release booking holds

  • Notify staff that documents are ready

  • Process final payments

  • Update booking status

  • Send to external systems

  • Create follow-up tasks

  • Generate signed document copies


Configuration

This trigger requires no additional configuration. It automatically triggers when all required documents for a booking are signed.


Available Data

When this trigger fires, it provides a booking object with comprehensive booking information, including document signing status.

Booking Object Structure

The booking object includes all standard booking fields. You can check document-related information through booking properties.

Accessing Booking Data

{booking.id} 
{booking.customer_id}
{booking.confirmed_at}

Note: Document-specific details are available through the booking model. The trigger fires when the signing process is complete.


Example Workflows

1. Send Completion Confirmation

Workflow Steps:

  1. Trigger: Documents Signed Complete

  2. Action: Get Booking (if needed)

  3. Action: Send Notification

    • To: {booking.customer.email}

    • Subject: "Documents Signed - Booking Confirmed"

    • Body: Confirmation that all documents are complete

2. Process Final Payment

Workflow Steps:

  1. Trigger: Documents Signed Complete

  2. Action: Get Booking

  3. Condition: If final payment is pending

  4. Action (True): Send Webhook (process payment)

  5. Action: Update Booking (mark payment processed)

3. Notify Operations Team

Workflow Steps:

  1. Trigger: Documents Signed Complete

  2. Action: Get Booking

  3. Action: Send Notification

    • To: Operations team

    • Subject: "All Documents Signed for Booking {booking.id}"

    • Body: Booking details and next steps

4. Update External System

Workflow Steps:

  1. Trigger: Documents Signed Complete

  2. Action: Get Booking

  3. Action: Send Webhook

    • URL: External system endpoint

    • Payload: Booking and document completion status

5. Generate Document Copies

Workflow Steps:

  1. Trigger: Documents Signed Complete

  2. Action: Get Booking

  3. Action: Send Webhook

    • URL: Document generation service

    • Payload: Request signed document PDFs

  4. Action: Send Notification (attach documents)


Testing

When testing this trigger:

  1. Select a booking with all documents signed

  2. The workflow will use that booking's data

  3. Review execution logs to verify booking information

Test Data

The trigger provides access to bookings where:

  • All required documents are signed

  • Signatures match requirements

  • Booking is confirmed


Best Practices

  1. Verify completion - Ensure all documents are actually signed

  2. Get booking details - Use "Get Booking" action for full context

  3. Process promptly - Act on completed documents quickly

  4. Store documents - Archive signed documents securely

  5. Notify all parties - Inform customer, staff, and partners

  6. Handle errors - Set up notifications for processing failures


Related Documentation

Did this answer your question?