Integrations

Integrations connect external services to your workspace. From here you configure card payments (Stripe), the AI gateway (OpenRouter) and outbound webhooks. Credentials you enter are encrypted at rest and never shown in plaintext again after saving.

Open Integrations in the admin sidebar (under Setup, plug icon).

How each card works

The page shows one card per integration. Each card displays a status badge and the same set of actions:

Status	Meaning
Not connected	No credentials stored yet.
Connected	Configured and enabled.
Disabled	Configured but switched off.

• Configure / Edit — opens a side panel to enter or update credentials.
• Disconnect — removes the stored credentials after a confirmation prompt.

Secret fields (API keys, signing secrets) show only the last four digits once saved. Leave a secret field blank when editing to keep the stored value.

Stripe

Accept card payments for bookings and memberships. Open the configure panel and enter:

Field	Notes
Mode	Test or Live. Shown as a badge on the card.
Publishable key	Required (pk_test_… / pk_live_…).
Secret key	Required on the first save (sk_…). Leave blank later to keep the stored value.
Webhook endpoint URL	Read-only. Copy it into the Stripe dashboard under Developers → Webhooks.
Webhook signing secret	Optional (whsec_…). Required only if you wire up Stripe webhooks.

Tip

In the Stripe dashboard, subscribe the webhook endpoint to invoice.paid and customer.subscription.deleted, then paste the signing secret back into this panel.

Disconnecting removes the stored credentials and payments stop working until you reconfigure.

OpenRouter

An AI gateway used by downstream features such as the booking copilot and support assistant. The panel takes a single field:

Field	Notes
API key	Required on the first save (sk-or-v1-…). Leave blank later to keep the stored value.

If you disconnect OpenRouter, AI-backed features fall back to the platform’s default key, or fail if none is configured.

Webhook

POSTs a signed JSON payload to a URL of yours whenever a notification fires. The panel lets you:

• URL — the endpoint we POST notifications to. Required on the first save.
• Signing secret — generate one with Regenerate. The secret is shown once on generation, so copy it immediately; afterwards only the last four digits are displayed. Each request is signed with this secret so your endpoint can verify authenticity.
• Send test — available once a URL and secret exist. Fires a test payload and reports the HTTP status code on success, or the error on failure.

Note

Regenerating the signing secret invalidates the previous one — update your receiving endpoint with the new value.

Disconnecting removes the stored webhook URL and signing secret.