Skip to content

team-telnyx/ai / providers/claude/plugins/telnyx-platform/skills/telnyx-import-elevenlabs

telnyx-import-elevenlabs

Verified

Import ElevenLabs conversational AI agents into Telnyx. Preserves instructions, voice settings, tools, and call analysis. Supports all SDK languages.

FileKindSize
SKILL.mdskill md7.1 KB
---
name: telnyx-import-elevenlabs
description: >-
  Import ElevenLabs conversational AI agents into Telnyx. Preserves
  instructions, voice settings, tools, and call analysis. Supports
  all SDK languages.
user_invocable: true
metadata:
  author: telnyx
  product: import-elevenlabs
  compatibility: "Requires a Telnyx API key and an ElevenLabs API key stored as a Telnyx integration secret."
---

# Import ElevenLabs Agents into Telnyx

Migrate your ElevenLabs conversational AI agents to Telnyx in minutes. The import API pulls agent configurations directly from ElevenLabs using your API key and recreates them as Telnyx AI Assistants.

**Interaction model**: Collect the user's Telnyx API key and ElevenLabs API key, store the ElevenLabs key as a Telnyx integration secret, run the import, then verify. Do NOT skip the secret-creation step — the import endpoint requires a secret reference, not a raw key.

## What Gets Imported

| Component | Imported? | Notes |
|-----------|-----------|-------|
| Instructions | Yes | Imported as-is |
| Greeting / first message | Yes | Maps to assistant `greeting` |
| Voice configuration | Yes | ElevenLabs voice ID and settings preserved |
| Dynamic variables | Yes | Default values carried over |
| Tools (hangup, transfer, webhook) | Yes | Tool definitions and configurations |
| MCP Server integrations | Yes | Server URLs and tool mappings |
| Call analysis / insights | Yes | Mapped to `insight_settings` |
| Data retention preferences | Yes | Mapped to `privacy_settings` |
| Knowledge base | **No** | Must be manually added post-import |
| Secrets (API keys in tools) | **Partial** | Placeholder secrets created — you must re-enter values in the Telnyx portal |

## Prerequisites

1. **Telnyx API key** — get one at https://portal.telnyx.com/#/app/api-keys
2. **ElevenLabs API key** — from your ElevenLabs dashboard (Profile → API Keys)
3. Store the ElevenLabs API key as a Telnyx integration secret at https://portal.telnyx.com/#/app/integration-secrets

## Step 1: Store Your ElevenLabs API Key as a Telnyx Secret

Before importing, store your ElevenLabs API key as an integration secret in Telnyx. Note the secret reference name (e.g., `elevenlabs_api_key`) — you'll use it in the import call.

You can create integration secrets via the Telnyx Portal under **Integration Secrets**, or via the API.

## Step 2: Import All ElevenLabs Agents

Import every conversational AI agent from your ElevenLabs account:

### curl

```bash
curl \
  -X POST \
  -H "Authorization: Bearer $TELNYX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "provider": "elevenlabs",
  "api_key_ref": "elevenlabs_api_key"
}' \
  "https://api.telnyx.com/v2/ai/assistants/import"
```

### Python

```python
import os
from telnyx import Telnyx

client = Telnyx(api_key=os.environ.get("TELNYX_API_KEY"))

assistants = client.ai.assistants.imports(
    provider="elevenlabs",
    api_key_ref="elevenlabs_api_key",
)

for assistant in assistants.data:
    print(f"Imported: {assistant.name} (ID: {assistant.id})")
```

### JavaScript

```javascript
import Telnyx from 'telnyx';

const client = new Telnyx();

const assistants = await client.ai.assistants.imports({
  provider: 'elevenlabs',
  api_key_ref: 'elevenlabs_api_key',
});

for (const assistant of assistants.data) {
  console.log(`Imported: ${assistant.name} (ID: ${assistant.id})`);
}
```

### Go

```go
assistants, err := client.AI.Assistants.Imports(context.TODO(), telnyx.AIAssistantImportsParams{
    Provider:  telnyx.AIAssistantImportsParamsProviderElevenlabs,
    APIKeyRef: "elevenlabs_api_key",
})
if err != nil {
    panic(err.Error())
}
for _, a := range assistants.Data {
    fmt.Printf("Imported: %s (ID: %s)\n", a.Name, a.ID)
}
```

### Java

```java
import com.telnyx.sdk.models.ai.assistants.AssistantImportsParams;
import com.telnyx.sdk.models.ai.assistants.AssistantsList;

AssistantImportsParams params = AssistantImportsParams.builder()
    .provider(AssistantImportsParams.Provider.ELEVENLABS)
    .apiKeyRef("elevenlabs_api_key")
    .build();
AssistantsList assistants = client.ai().assistants().imports(params);
assistants.getData().forEach(a ->
    System.out.printf("Imported: %s (ID: %s)%n", a.getName(), a.getId()));
```

### Ruby

```ruby
assistants = client.ai.assistants.imports(
  provider: :elevenlabs,
  api_key_ref: "elevenlabs_api_key"
)

assistants.data.each do |a|
  puts "Imported: #{a.name} (ID: #{a.id})"
end
```

## Step 2 (Alternative): Import Specific Agents

To import only certain agents, pass their ElevenLabs agent IDs in `import_ids`:

### curl

```bash
curl \
  -X POST \
  -H "Authorization: Bearer $TELNYX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "provider": "elevenlabs",
  "api_key_ref": "elevenlabs_api_key",
  "import_ids": ["elevenlabs-agent-id-1", "elevenlabs-agent-id-2"]
}' \
  "https://api.telnyx.com/v2/ai/assistants/import"
```

### Python

```python
assistants = client.ai.assistants.imports(
    provider="elevenlabs",
    api_key_ref="elevenlabs_api_key",
    import_ids=["elevenlabs-agent-id-1", "elevenlabs-agent-id-2"],
)
```

### JavaScript

```javascript
const assistants = await client.ai.assistants.imports({
  provider: 'elevenlabs',
  api_key_ref: 'elevenlabs_api_key',
  import_ids: ['elevenlabs-agent-id-1', 'elevenlabs-agent-id-2'],
});
```

## Step 3: Verify the Import

List your Telnyx assistants to confirm the import succeeded:

### curl

```bash
curl -H "Authorization: Bearer $TELNYX_API_KEY" \
  "https://api.telnyx.com/v2/ai/assistants"
```

### Python

```python
assistants = client.ai.assistants.list()
for a in assistants.data:
    print(f"{a.name} — {a.id} — imported: {a.import_metadata}")
```

### JavaScript

```javascript
const assistants = await client.ai.assistants.list();
for (const a of assistants.data) {
  console.log(`${a.name} — ${a.id} — imported:`, a.import_metadata);
}
```

## Step 4: Post-Import Checklist

After importing, complete these manual steps:

1. **Re-enter secrets** — Any API keys referenced by tools were imported as placeholders. Go to https://portal.telnyx.com/#/app/integration-secrets and supply the actual values.
2. **Add knowledge bases** — Knowledge base content is not imported. Upload files or add URLs in the assistant's Knowledge Base settings.
3. **Assign a phone number** — Connect a Telnyx phone number to your imported assistant to start receiving calls.
4. **Test the assistant** — Use the Telnyx assistant testing API or make a test call to verify behavior.

## Re-importing

Running the import again for the same ElevenLabs agents will **overwrite** the existing Telnyx copies with the latest configuration from ElevenLabs. This is useful for syncing changes during a gradual migration.

## API Reference

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `provider` | string | Yes | Must be `"elevenlabs"` |
| `api_key_ref` | string | Yes | Name of the Telnyx integration secret containing your ElevenLabs API key |
| `import_ids` | array[string] | No | Specific ElevenLabs agent IDs to import. Omit to import all. |

Endpoint: `POST https://api.telnyx.com/v2/ai/assistants/import`

Full API docs: https://developers.telnyx.com/api-reference/assistants/import-assistants-from-external-provider
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall