API keys and integrations
Keys for your servers and the Chrome extension, webhooks, Segment and connected apps.
These are usually set up by a developer. This page tells you what each one is for and where it lives; the developer guides have the details.
API keys
Settings → API keys holds secret API keys, for the Chrome extension and for your own servers and scripts. A key acts as the person who created it, with their current role, in this workspace.
- Give each key a name you'll recognise later, such as "Staging server" or "CI".
- Never put a secret key in your website's code. The snippet uses a separate, publishable key.
- Revoke a key the moment you stop needing it, or if it leaks.
Developer guide: Keys and the REST API.
Integrations
Settings → Integrations (you need the Workspace settings permission):
- Webhooks — Cueston tells your systems when something happens: content is published, a review is requested or decided, someone completes or dismisses guidance, a survey is answered, someone joins. See Webhooks.
- Segment — send what people do with your guidance to Segment, and use Segment traits and events to target guidance. See Segment.
- AI agents (MCP) — let Claude, ChatGPT and other AI assistants work in your workspace. See Work with Claude or ChatGPT.
- Connected apps — the AI assistants and other apps people have connected, and a way to disconnect them.
Your users' data
Settings → Data & privacy sets how long Cueston keeps what it records about your users, and lets you find, download or delete one person's data for privacy requests. See End-user data.