Retell integration

How do I connect a Retell tool to one protected action?

Current package set: Core rc.1, Runtime preview.5 and Actions preview.8. Try HTTP reference preview.4 or Retell adapter preview.3 with equipment example preview.4.

Version history and scope

Retell preview.1 declarations describe the older Runtime preview.1 / Actions preview.2 line. Retell preview.2 uses a mock facade; HTTP preview.1 simulates bookkeeping. The older private HTTP source uses Runtime preview.3 / Actions preview.4. These are separate from the current runnable examples.

Examples use local test systems. They do not validate live providers, arbitrary crashes or distributed durability. Approved participants can use protected downloads.

Connect a Retell custom tool to one protected action in your backend. The current Retell adapter 0.2.0-preview.3 and equipment example 0.2.0-preview.4 use Core rc.1, Runtime preview.5 and Actions preview.8. The equipment example executes Actions against a local test equipment service; it is not live Retell-provider validation.

Run the current Retell example. For a first integration without a voice provider, start with the runnable HTTP example.

Keep your backend in control

Authenticate incoming tool calls and derive tenant and actor context in your backend. The adapter consumes Actions results; it is not a Retell SDK, provider client or hosted webhook. Provider acknowledgment alone does not establish an effect. Render only a matching returned permitted claim; retain UNKNOWN and verify without redispatch.

Replay and recovery

A saved response supports duplicate replay, not live reconciliation authority. Live reconciliation needs the exact Actions-owned UNKNOWN in the same runtime/process. Exported-record recovery is a separate host-authorized verifier-only path. Follow the current supplied README for the adapter API and the recovery paths.

Historical versions

Preview.1 API declarations use Runtime preview.1 / Actions preview.2; they do not describe adapter preview.3. Preview.2 is a mock Actions example, not the current executable equipment example. Historical API declarations.