Embedding Kinetic into existing websites, apps & platforms

Four integration surfaces, from one script tag to full automation pipelines.

1. Chat widget install (websites)

The fastest integration. Paste this before </body>:

<script
  src="https://kinetic-4g1.pages.dev/widget/kinetic-chat.js"
  data-org-id="YOUR_ORG_ID"
  data-color="#6366f1"
  data-position="bottom-right"
  data-greeting="Hi! How can we help you today?">
</script>

Attributes

Attribute	Required	Description
`data-org-id`	Yes	Your Org ID from the Business Centre. Missing it logs a console warning and the widget stays hidden.
`data-color`	No	Bubble color. Defaults to Kinetic indigo.
`data-position`	No	`bottom-right` (default) or `bottom-left`.
`data-greeting`	No	First message shown in the chat.
`data-api`	No	Override the API base if you self-host or proxy.

2. Full chat surface embed

To give a page its own chat view (support portals, in-app webviews), embed the standalone chat page in an iframe:

<iframe
  src="https://kinetic-4g1.pages.dev/chat/?orgId=YOUR_ORG_ID"
  style="width:100%;height:600px;border:0;border-radius:12px"
  title="Chat with us">
</iframe>

The surface shows brand, online status, typing dots, and the message log — connected to the same Copilot and inbox as every other channel.

3. Webhooks (inbound events)

Kinetic exposes verified webhook endpoints for channel platforms:

WhatsApp Cloud API webhook — handshake via ?hub.verify_token=…; point your Meta app subscription at the platform's WhatsApp endpoint.
Telegram webhook — set your bot's webhook to the Telegram endpoint and configure the secret token header (x-telegram-bot-api-secret-token) so updates are authenticated.
Payment callbacks — payment providers call back with signature headers which are verified before wallets are credited.

Webhook secrets live in server configuration. Rotate them through your deployment environment variables — never in client code or repositories.

4. n8n automation recipes

Kinetic runs n8n internally (400+ connectors). Recipes that work out of the box:

Recipe	Flow
Daily business summary	Cron trigger → fetch day's orders/conversations → format → send via channel client.
E-commerce sync	Store webhook → map product/order payload → update catalog & notify owner on WhatsApp.
Gmail / Google Workspace triage	New email → classify with Copilot → create task or reply draft for approval.
Lead enrichment handoff	New lead scored → enrich via research tools → post to Slack/Telegram.
Connector governance	External tool calls pass policy checks before execution; denials are logged.

5. API keys & scopes

Credential	Who holds it	Scope
Org ID	Public (widget/iframe)	Identifies the tenant for inbound customer chat only.
Tenant session/token	Tenant users	All portal operations for that tenant only.
Admin session	Platform operators	Admin plane: tenants, harnesses, incidents.
`DEVELOPER_API_KEY`	Engineers / CI	Developer API: health, cost intelligence, infrastructure read-outs. Sent as `x-developer-api-key`.

Principle of least privilege: browser integrations get the Org ID only. Anything that can write data or spend units stays server-side.