Skip to content

fix(sdk): clarify section about secrets #406

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
adkah merged 2 commits into from
Feb 2, 2026
Merged

fix(sdk): clarify section about secrets #406

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
619be5a
fix(sdk): clarify section about secrets
adkah Feb 2, 2026
e5c225a
remove second period
adkah Feb 2, 2026
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
2 changes: 1 addition & 1 deletion integrations/sdk/integration/concepts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -181,7 +181,7 @@ Just like states, tags can be used as a form of memory, enabling the integration

Integrations can define secrets, such as API keys, tokens, or other sensitive values. While they're most often used for authentication with external services, they can represent any sensitive information required by the integration.

Secrets are defined in the integration definition. When deploying the CLI prompts for secrets and prevents deployment if a required secret is omitted. The secret values are then available at runtime for the integration developer to use.
Secrets are defined in the integration definition. When deploying an integration, the CLI prompts for any secrets (and prevents deployment if a required secret is omitted). The secret values are then available at runtime for the integration developer to use.

Secrets are global to the integration and aren't scoped to individual bots.

Expand Down