Docs/Integrations

Integrations

Integrations connect BookFlow with outside systems. The vendor does not need to understand every API detail, but they do need to know what each connector sends, receives, simulates, maps, and proves in the activity log.

Integration Hub

Integrations admin page — The integrations page has health, provider tabs, Lead Intake, Activity, and Contracts.

Connector Map

Connector impact map — Provider-by-provider view of what changes when an outside app sends or receives data.

Connector	Plain meaning	Connected BookFlow area
CRM	Imports sales leads and can push booking usage events back.	Lead Intake, bookings, customer profiles, external mappings.
HR	Syncs staff, branches, and leave/time-off data.	Staff profiles, locations, availability engine.
TicketPro	Creates support tickets from customer conversations.	Receptionist, customer support, booking context.
Ecommerce	Consumes paid orders and turns them into benefits.	Memberships, packages, vouchers, customer wallet.
FlowOS	Bridges receptionist messages and booking lifecycle webhooks.	Assistant conversations, booking created/rescheduled/cancelled/completed events.
Custom Apps	Accepts signed custom workflow payloads.	Local records, entitlements, mappings, and activity proof.

How The Page Works

Health

Shows active connectors, stale connectors, failed runs, webhook readiness, attention items, and provider counters.

Provider tabs

Each connector has its own form, status, test action, sync action, webhook URL, secret, and contract summary.

Lead Intake

CRM leads can be converted into BookFlow bookings by choosing service, location, staff, date, and time.

Activity

Every test, sync, or webhook run can be filtered and inspected. This is where debugging starts.

CRM Lead Flow

CRM lead->Sync log->Lead Intake->Vendor chooses slot->Booking created->External mapping saved

The external mapping is important. It is the record that says "this outside CRM lead is now this BookFlow booking."

FlowOS Contracts And Custom Apps

FlowOS is the receptionist and lifecycle bridge. BookFlow can send booking lifecycle payloads outward and can receive assistant-style conversation context depending on configuration. Custom Apps use the same contract idea for buyer-specific workflows: signed payload, mapped fields, local result, external mapping, and activity proof.

Path	What moves	Local result
FlowOS outbound	Booking created, rescheduled, cancelled, completed, and receptionist lifecycle events.	Activity log and external delivery proof.
FlowOS inbound	Conversation or channel context from web chat, WhatsApp, SMS, or phone style flows.	Receptionist context and follow-up queue.
Custom app event	Signed buyer-defined payload with mapped customer, booking, or entitlement data.	Local booking/support/benefit record plus external mapping.

CRM And TicketPro Story

CRM path

Lead to booking to campaign proof

CRM is the sales and marketing system. BookFlow pulls qualified leads into Lead Intake, lets the vendor convert one into a normal booking, pushes booking usage events back when configured, and can create a paused paid ad draft in CRM from Programs.

BookFlow does not publish Meta/Facebook or Google ads directly. The CRM keeps ad accounts, provider credentials, approval, activation, publishing, and audit control.

TicketPro path

Support handoff with duplicate protection

TicketPro is the support owner when active. A customer support request or AI receptionist follow-up can create one requester ticket with booking/customer/transcript context. BookFlow stores the ticket reference and locks repeat follow-up.

If TicketPro is inactive, the same conversation can be resolved locally once. Local conversations can be reopened; TicketPro-owned conversations stay owned by TicketPro.

Webhook Chain

Outside system sends event->BookFlow verifies webhook->Connector handles payload->Local records update->Activity log records result

Warning: Webhook secrets are sensitive. They prove the event came from the expected connection.

Simulator And Support Diagnostics

The demo uses simulator and seeded replay paths for external systems that should not be called from a buyer demo. For support, start with the Integrations Activity tab, then use system preflight or a redacted support bundle when the issue crosses hosting, mail, storage, scheduler, provider, or webhook configuration.

Simulator replay

Runs a known CRM, ecommerce, TicketPro, FlowOS, or custom app payload through the same mapping and activity path.

Activity drawer

Shows provider, direction, endpoint, request payload, response payload, status, and error text for debugging.

Support bundle

Creates a redacted ZIP with preflight data and support-safe runtime evidence.

Contracts

Contracts explain what the connector expects. For a non-technical user, treat a contract like a checklist between BookFlow and the outside system: authentication, endpoints, inbound events, and outbound events.

Workflow Playbooks

Start here

Integration Workflow Manual

Explains what happens when CRM, HR, TicketPro, Ecommerce, FlowOS, or a custom app connects, runs, maps payloads, and updates BookFlow records.

Open integration manual

Scenario

Complete Demo Script

Shows where integrations fit in the end-to-end Nimbus demo: event comes in, BookFlow updates a record, operator sees the result.

Open demo script

Detailed Screen Reference

For every connector field, health chart, lead conversion field, activity table column, contract item, and mapping explanation, open Integrations And Settings Reference.