NativeConnection required
Calendar conflict protection and booking updates
Google Calendar · Microsoft Outlook
Read Google and Microsoft busy time and send supported booking changes to the configured calendar.
Provider evidence required
Connected booking operations
Every connection should say what it actually does.
Flexboox links booking demand to calendars, payments, communication, CRM systems, and automation. Native connections, provider-specific connectors, and webhooks remain visibly distinct.
No equal-looking logo wall
Provider data consequences stay explicit
Failures remain reviewable
Plan and provider setup requirements are visible
One booking state
Connected handoffs
Calendar
Busy time and appointment updates
Payments
Deposit or full payment state
External systems
Configured customer and booking handoff
Integration depth
Recognisable tools, labelled honestly.
The label describes the implementation relationship—not the size of the logo or the popularity of the provider.
NativeDirect connection built into Flexboox
ConnectorProvider-specific delivery and setup
Via webhookBooking events sent to an automation URL
Calendar
Google Calendar
Native
Microsoft Outlook
Native
Payments
Stripe
Native
Mollie
Native
Communication
Twilio
Native
Resend
Native
CRM
HubSpot
Connector
Salesforce
Connector
Pipedrive
Connector
Automation
Zapier
Via webhook
Make
Via webhook
Availability depends on the Flexboox plan, provider account, and workspace configuration. All product names and logos are trademarks of their respective owners. Twilio and all related logos are trademarks of Twilio Inc. or its affiliates.
Native connections
Keep the booking state connected to delivery.
NativeConnection required
Booking payments
Stripe · Mollie
Collect configured deposits or full payments through Stripe or Mollie and reconcile provider callbacks with the booking.
Provider evidence required
NativeConnection required
Customer communication
Resend · Twilio
Send configured email and SMS messages with delivery outcomes available to the workspace operation.
Provider evidence required
Calendar capability detail
Calendar connections do not imply identical or fully symmetric behavior. Availability also depends on provider connection, account permissions, and release certification.
| Operation | Google CalendarProvider evidence required | Microsoft OutlookProvider evidence required |
|---|---|---|
| Busy time blocks booking conflicts | Supported | Supported |
| Flexboox creates, updates, and removes calendar events | Supported | Supported |
| External calendar changes update Flexboox | Limited | Not supported |
Limited means the provider has some inbound handling but Flexboox does not claim a complete two-way event-ownership contract.
CRM and ERP connectors
Choose the customer handoff your team needs.
Connector setup names the credential or endpoint required and explains what customer or booking data is delivered.
Pipedrive
Creates a person from customer details when a booking is confirmed.
ConnectorHubSpot
Creates a contact from customer details when a booking is confirmed.
ConnectorSalesforce
Creates a contact through the configured Salesforce instance URL.
ConnectorTeamleader
Posts customer and booking details to the configured compatible endpoint.
ConnectorOdoo
Posts customer and booking details to the configured Odoo endpoint.
ConnectorWebhooks and automation
Send booking events to the workflow you already run.
Custom webhooks can deliver configured booking events to Make, Zapier, n8n, or an internal HTTPS endpoint. Optional bearer credentials and HMAC signing are available during setup.
Discuss your workflowVia webhook
Booking event delivery
Trigger
Booking confirmed or changed
Protection
Optional bearer token and HMAC signature
Operational result
Delivery attempt and failure state remain reviewable
Connect when the operation needs it
Keep every booking handoff visible and intentional.
Start with calendars and payments, then add communication, connector handoffs, and webhooks as the booking operation grows.