Integrations Workflow
Integrations should be configured only when the workspace has a clear use for them and an owner who can maintain them.
Outcome
At the end:
- Each enabled integration has credentials, consent posture, public-site behavior, and an operator owner.
- Customer-facing effects are tested.
- Failure modes and rollback steps are known.
Do not treat a green connection badge as the finish line. An integration is ready only when the console can show its state, the public site behaves as expected, and an operator knows what to do if the provider disconnects or reports delayed data.
Integration Map
Stripe Connect
Console surface: Payments, Checkout and Tax
Sites effect: Product checkout, booking payments, invoices, refunds
GA4
Console surface: Integrations > Google Analytics
Sites effect: Public traffic measurement
Google Ads
Console surface: Integrations > Google Ads
Sites effect: Tag load and booking conversion events
Google Business Profile
Console surface: Integrations > Google Business Profile
Sites effect: Reviews and listing data
Google Calendar
Console surface: Scheduling > Calendar Sync
Sites effect: Availability conflicts and event sync
Domain and DNS
Console surface: Domain and Email
Sites effect: Public routing and branded links
Email sender
Console surface: Domain and Email, Email Notifications
Sites effect: Customer notifications
Shipping provider
Console surface: Shipping
Sites effect: Rates, labels, tracking
Webhooks
Console surface: App routes and service configuration
Sites effect: Cache invalidation and event processing
Console Setup Preview
Use this preview before touching credentials. It names what the operator should see in the console and what must become true on the public site.
Payments
Expected console state: Stripe account status, requirements, payouts, checkout/tax controls
Public verification: Checkout creates a payment and writes an order or booking
Analytics
Expected console state: GA4 Measurement ID, enable state, consent posture
Public verification: Tag appears only when analytics consent allows it
Ads
Expected console state: Conversion ID, conversion label, consent mode, acknowledgement
Public verification: Booking confirmation can fire a deduped conversion when allowed
Business Profile
Expected console state: Connected Google account, selected listing, sync status
Public verification: Reviews/listing data appear where surfaced
Calendar
Expected console state: Provider, selected calendar, staff mapping, sync health
Public verification: External conflicts affect availability
Domain and email
Expected console state: DNS records, verification, sender identity, reply-to
Public verification: Final domain resolves and notifications use intended sender
Shipping
Expected console state: Origin, package presets, zones, carrier/provider status
Public verification: Checkout estimates shipping and fulfillment can create labels
Webhooks
Expected console state: Authorized route, event family, recent delivery state
Public verification: Console save updates the matching public surface
The setup card is not done until it has a visible owner, a healthy state, a tested public effect, and a rollback path.
Stripe Connect
Configure:
- Open Payments.
- Connect Stripe.
- Complete requirements.
- Review payouts and fees.
- Configure Checkout and Tax.
- Test product checkout.
- Test booking payment if bookings are paid.
- Test refund or cancellation behavior.
Verify:
- Payment account status is clear.
- Public checkout can complete.
- Console receives payment state.
- Customer portal shows resulting order or booking.
Setup preview:
Payments overview
Operator should verify: Account connected, requirements visible, payout posture understood
Checkout and Tax
Operator should verify: Collection, tax, shipping, discount, and payment-method behavior match launch intent
Orders or bookings
Operator should verify: Paid customer action writes the expected record and status
Customer portal
Operator should verify: The customer sees only their order, booking, invoice, or payment state
Refund/cancel path
Operator should verify: Staff know the exact console surface for reversal or amendment
Rollback:
- Disable checkout.
- Hide paid products or services.
- Pause ads.
- Keep the site live if non-payment content still works.
Google Analytics
Configure:
- Create or choose a GA4 property.
- Copy Measurement ID.
- Open Integrations > Google Analytics.
- Paste ID.
- Confirm cookie consent behavior.
- Enable.
- Verify public tag load after consent conditions.
Expected ID: G-XXXXXXXXXX.
Setup preview:
Google Analytics card
Operator should verify: Measurement ID is present, valid-looking, and enabled
Privacy settings
Operator should verify: Analytics consent behavior is intentional
Public site
Operator should verify: GA4 tag appears only after the allowed consent state
Insights handoff
Operator should verify: Operators understand that provider reports may lag
Rollback:
- Disable GA4 integration.
- Leave public site running.
Google Ads
Configure:
- Copy Google Ads Conversion ID.
- Copy conversion action label if explicit conversion events are needed.
- Open Integrations > Google Ads.
- Enter ID and label.
- Choose consent mode.
- Complete acknowledgements.
- Test booking confirmation.
Expected Conversion ID: AW-123456789.
Verify:
- Tag loads only when allowed.
- Global Privacy Control suppresses advertising signals.
- Booking confirmation conversion does not send access tokens in URL data.
- Duplicate confirmation views do not over-count within the same session.
Setup preview:
Google Ads card
Operator should verify: Conversion ID and label are entered in the right workspace
Consent controls
Operator should verify: Marketing consent and Global Privacy Control behavior are understood
Booking confirmation
Operator should verify: Conversion fires only once for the same browser session when allowed
Campaign handoff
Operator should verify: Ads owner knows when to pause campaigns if attribution is untrusted
Rollback:
- Disable Google Ads.
- Pause ad campaigns if attribution is untrusted.
Google Business Profile
Configure:
- Open Integrations > Google Business Profile.
- Connect Google account.
- Select listing.
- Confirm status.
- Verify reviews or listing data in the console.
Failure checks:
- Google account must have listing access.
- Workspace must map to the intended listing.
- Reconnect if token state is invalid.
Setup preview:
Google Business Profile card
Operator should verify: Connected account, selected listing, and sync status are visible
Reviews surface
Operator should verify: Synced reviews match the intended location
Reputation workflow
Operator should verify: Staff know where review data appears and when to reconnect
Calendar Providers
Configure:
- Open Scheduling > Calendar Sync.
- Connect provider.
- Select calendar.
- Confirm sync status.
- Test conflict.
- Create booking and verify event sync.
Failure checks:
- Token expired.
- Wrong calendar selected.
- Staff not assigned.
- Availability does not read external conflicts.
Setup preview:
Scheduling calendar sync
Operator should verify: Provider connected, calendar selected, sync state healthy
Staff/service mapping
Operator should verify: Bookable services use the intended staff or resource calendar
Public booking step
Operator should verify: External conflicts remove unavailable times
Operations handoff
Operator should verify: Staff know where to resolve token or calendar mismatch issues
Domain And Email
Configure:
- Open Domain and Email.
- Add domain.
- Add DNS records.
- Verify domain.
- Configure sender identity.
- Verify notifications from the final domain.
Failure checks:
- DNS proxy can break email records.
- Links can point to an old host.
- Login callback domain may differ from public domain.
Setup preview:
Domain settings
Operator should verify: Final domain, DNS checks, and verification status are clear
Email sender
Operator should verify: Sender identity, reply-to, and notification templates match launch intent
Public site
Operator should verify: Final URL resolves, auth callbacks return to the right host, social previews match
Support workflow
Operator should verify: Operators know where failed DNS and sender checks are surfaced
Shipping Provider
Configure:
- Open Shipping.
- Add origin.
- Add packages.
- Add zones.
- Add rates.
- Connect provider if labels are purchased.
- Test label purchase.
Failure checks:
- Missing weight or dimensions.
- Invalid address.
- Carrier does not support selected package mode.
- Provider credentials invalid.
Setup preview:
Shipping dashboard
Operator should verify: Origin, zones, packages, and provider status are visible
Product catalog
Operator should verify: Shippable products have weight, dimensions, and fulfillment expectations
Checkout
Operator should verify: Shipping estimate appears only when address and cart support it
Fulfillment
Operator should verify: Label, tracking, and exception state have an operator owner
Webhooks And Revalidation
Webhook categories may include:
- Branding.
- Settings.
- Domains.
- Products.
- Bookings.
- Pages.
- Forms.
- Help.
- Media.
- Stripe.
- Shipping.
Use webhook categories to connect a console save to the public route that should update. If a page, product, help article, domain preview, or checkout state looks stale, confirm the owning category before forcing a broad cache refresh or changing unrelated content.
Verify:
- Console save triggers expected public update.
- Webhook request is authorized.
- Public cache is invalidated or revalidated.
Setup preview:
Brand save
Expected public update: Header, logo, theme, favicon, and previews refresh
Product save
Expected public update: Shop, product detail, cart validation, and checkout state refresh
Service save
Expected public update: Booking service list and detail refresh
Availability change
Expected public update: Public time slots refresh
Page publish
Expected public update: Public page route, navigation, and sitemap refresh
Form publish
Expected public update: Public form schema refreshes
KB article publish
Expected public update: Help center and article route refresh
Domain change
Expected public update: Routing and preview surfaces refresh
Integration Done Criteria
Use this list before enabling an integration for real customer traffic, live reporting, or launch approvals. Missing ownership or rollback is a launch risk even when credentials are valid.
- Integration has an owner.
- Credentials are valid.
- Consent/legal posture is understood.
- Public behavior is tested.
- Console receives expected state.
- Rollback is known.
Validation Packet
Record this packet after each integration is enabled:
Workspace
What to record: Name, slug, and final public URL
Integration owner
What to record: Person responsible for maintaining credentials and provider health
Console evidence
What to record: Exact console surface and healthy state observed
Public evidence
What to record: Route or customer action used for verification
Consent/legal state
What to record: Analytics, ads, email, or privacy posture if relevant
Provider evidence
What to record: Account, listing, calendar, payment, shipping, or tag identifier
Rollback
What to record: Exact setting or operational step to disable the integration
Retest date
What to record: When the integration should be checked again
This packet makes integration support repeatable after the launch owner hands off the workspace.