Skip to content

Add note about Superwall API key usage #216

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DreamingInBinary merged 1 commit into from
Jun 17, 2026
Merged

Add note about Superwall API key usage #216

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions content/docs/agents/settings.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,15 @@ Use **Environment** for variables that tools on the hosted machine can read.

Some integration variables are reserved. `SUPERWALL_API_KEY` comes from the organization selector. `GH_TOKEN`, `GITHUB_TOKEN`, and `SLACK_BOT_TOKEN` come from the GitHub and Slack connection flows.

<Note>
**Need a Superwall API key?** In Superwall Agents, select your organization in
the chat header. Agents provides a managed organization API key to new turns,
so you usually do not add `SUPERWALL_API_KEY` here. For an external agent,
custom tool, or local script, create an organization API key in
[Settings > API Keys](/dashboard/dashboard-settings/overview-settings-access-controls#api-key-access).
Do not use the public `pk_` SDK key for server or API access.
</Note>

<Warning>
Do not paste secret values into chat. Store them in Environment so tools can
use them without adding the secret to conversation history.
Expand Down
Loading