Docs navigation
Connect workspace integrations
Set up analytics, agent activity, playbook destinations, article drafts, and the weekly Slack digest from Settings.
Updated
At a glance
-
Pick a connection
Open Settings → Integrations and choose the service your team uses.
-
Finish its setup
Authorize the service, then select a property, zone, page, or space when asked.
-
Check its status
Return to the integration card for sync status, reconnect actions, and delivery controls.
Open Settings → Integrations in the console. Each connection belongs to your workspace. Select an integration to see its setup and current status. A Setup label means authorization or destination selection is still unfinished; Attention means the connection needs review.
Connect the service you need
| Service | What it brings into or sends from KnitKnot | Setup in the console |
|---|---|---|
| Google Analytics | Sessions referred from AI assistants | Select Connect, authorize Google, then choose the GA4 property. |
| Cloudflare | Verified agent requests and AI-referred visits at the edge | Select Connect, authorize Cloudflare, then choose the account and zones to import. |
| Notion | Playbooks in a Notion database, with status and shipped URL changes flowing back | Select Connect, authorize Notion, then choose the page where KnitKnot should create the database. |
| GitBook | Draft articles in a GitBook space for your team to review | Select Connect, paste a GitBook API token, then choose the space. |
| Slack | Weekly score, movement, and next-action digest | Select Connect and paste an incoming webhook URL from your Slack workspace. |
For Cloudflare, choose the zones that serve the pages you want measured. The card shows analytics and history-import status after setup. A historical import can take time; Retry history import appears when the import is partial or degraded. Google Analytics and Cloudflare count different events, so keep their AI referral totals separate in Read agent activity and AI referrals.
For Notion, authorization alone is not the last step. Choose a destination page to create the playbook database. Once connected, Sync now starts a manual playbook sync; KnitKnot also checks for changes made in Notion. GitBook likewise needs a space after the token is accepted.
Set Slack delivery
Connecting a Slack webhook starts the digest in Shadow mode. The KnitKnot team reviews it before delivery goes live. Open Slack digest settings to switch delivery to Live, or pause the weekly digest without disconnecting. Use the card’s test action to check that Slack accepts the webhook.
If Slack says the webhook cannot be reached, reconnect it with a working incoming webhook URL. A connected Slack card alone does not mean weekly messages are being delivered to the channel: check whether delivery is Shadow, Live, or Paused.
When a connection needs attention
Open the card marked Setup to finish choosing its destination. Use Reconnect if access has expired or permissions changed. For Cloudflare, approve the requested Zone Analytics permission if the card says activity import requires it. A failed import or sync should remain visible on the card; check that status before interpreting an empty traffic or playbook view.
Use Disconnect only when you intend to stop the connection. The confirmation dialog explains the effect for each service. In particular, disconnecting Google Analytics stops its daily sync and deletes the collected traffic history; reconnecting starts fresh. Disconnecting Notion leaves pages already in Notion in place but stops updates. Disconnecting GitBook removes the stored token while leaving existing GitBook pages untouched.
For what each traffic source means after connection, see Read agent activity and AI referrals. For playbook work, start with Issues and playbooks.