> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Prepare an integration

> Prepare credentials, environment values, configuration versions, and phone resources before a supported runtime integration is released.

An integration needs the right configuration, resource access, and environment values. Prepare those independently from the runtime path that will eventually serve a conversation.

## Integration checklist

<Steps>
  <Step title="Identify the configuration">Keep the agent, branch, and version IDs for the reviewed configuration. Read the settings back before using them in an integration.</Step>
  <Step title="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.</Step>
  <Step title="Review environment values">Define required strings and credential references for the intended environment. Understand production fallback before using another environment name.</Step>
  <Step title="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.</Step>
  <Step title="Verify the complete integration">When the runtime path is released, test authentication, resource access, connection, failure handling, and stored results together using controlled data.</Step>
</Steps>

## Guides

<CardGroup cols={2}>
  <Card title="Versions and drafts" icon="code-branch" href="/agents-platform/deploy/versioning">Review the configuration you intend to connect.</Card>
  <Card title="Environment variables" icon="sliders" href="/agents-platform/deploy/environment-variables">Manage workspace values and credential references.</Card>
  <Card title="Access and credentials" icon="key" href="/agents-platform/configure/authentication/overview">Separate server keys, dashboard sessions, and conversation access.</Card>
  <Card title="Phone configuration" icon="phone" href="/agents-platform/deploy/telephony/overview">Review provider records and calling prerequisites.</Card>
  <Card title="WhatsApp" icon="comments" href="/agents-platform/deploy/whatsapp/overview">Prepare a business account connection and review planned messaging and calling.</Card>
</CardGroup>

<Note>
  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.
</Note>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can a published version receive live traffic?" id="faq-version-traffic">A published version identifies saved configuration. Traffic allocation and execution require a separate released runtime path.</Accordion>
  <Accordion title="Do environment names create infrastructure?" id="faq-environment-infrastructure">No. Workspace environment values are configuration data. They do not create separate servers, deployments, databases, or workspaces.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.