Store credentials and bind them to Agents without exposing real values in examples.
Create a secret
Bind it to an Agent
Open secret bindings in the Agent editor.
Select a saved secret in the current Profile.
Reference its name in the business HTTP tool's request headers.
Save and use debugging to verify authentication.
Authorization: Bearer ${ORDER_API_TOKEN}
The placeholder name must match the bound secret. Creating a secret without binding it does not give the tool access to the credential.
If the runtime needs a credential file, configure a file binding with the path and decoding options shown in the UI. Use this only when the tool requires file-based credentials.
Update and delete
Updating replaces the value without changing the name. After rotating a token in the business system, update the corresponding entry and test a call.
Secrets referenced by Agents or sessions may not be deletable. Remove and save the bindings first. Credentials in an Agent's invocation URL serve a different purpose; see HTTP integration.