Integration checklist
1
Identify the configuration
Keep the agent, branch, and version IDs for the reviewed configuration. Read the settings back before using them in an integration.
2
Prepare credentials
Use a scoped server-side API key and the workspace credential workflow for provider access. Keep secrets out of browser bundles and prompt text.
3
Review environment values
Define required strings and credential references for the intended environment. Understand production fallback before using another environment name.
4
Check execution availability
Confirm that the intended channel and runtime path are supported by the released implementation. A saved number, version, or environment variable is not evidence that a live session can execute.
5
Verify the complete integration
When the runtime path is released, test authentication, resource access, connection, failure handling, and stored results together using controlled data.
Guides
Versions and drafts
Review the configuration you intend to connect.
Environment variables
Manage workspace values and credential references.
Access and credentials
Separate server keys, dashboard sessions, and conversation access.
Phone configuration
Review provider records and calling prerequisites.
Prepare a business account connection and review planned messaging and calling.
The documented signed-token initiation, traffic deployment, outbound calling, and automated response-test paths remain unavailable. This section prepares configuration and access; it does not provide a verified live deployment walkthrough.
Frequently asked questions
Can a published version receive live traffic?
Can a published version receive live traffic?
A published version identifies saved configuration. Traffic allocation and execution require a separate released runtime path.
Do environment names create infrastructure?
Do environment names create infrastructure?
No. Workspace environment values are configuration data. They do not create separate servers, deployments, databases, or workspaces.