mcpbeat Sign in

Telnyx Import Elevenlabs Agent Skill

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

2k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
201
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/team-telnyx/ai --skill telnyx-import-elevenlabs

The instruction itself

22 sections, as written by the author

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

  • Telnyx API key — get one at https://portal.telnyx.com/#/app/api-keys
  • ElevenLabs API key — from your ElevenLabs dashboard (Profile → API Keys)
  • 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

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

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

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

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

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

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

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

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

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

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

Python

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

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:

  • 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.
  • Add knowledge bases — Knowledge base content is not imported. Upload files or add URLs in the assistant's Knowledge Base settings.
  • Assign a phone number — Connect a Telnyx phone number to your imported assistant to start receiving calls.
  • 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

Other skills for the same job

different authors, same section of the catalogue
Pydicom
by christophacham
×3

Python library for working with DICOM (Digital Imaging and Communications in Medicine) files. Use this skill when reading, writing, or modifying medical imaging data in DICOM format, extracting pixel data from medical images (CT, MRI, X-ray, ultrasound), anonymizing DICOM files, working with DICOM metadata and tags, converting DICOM images to other formats, handling compressed DICOM data, or processing medical imaging datasets. Applies to tasks involving medical image analysis, PACS systems, radiology workflows, and healthcare imaging applications.

13k tokens scripts
Pydicom
by ComeOnOliver
×3

Python library for working with DICOM (Digital Imaging and Communications in Medicine) files. Use this skill when reading, writing, or modifying medical imaging data in DICOM format, extracting pixel data from medical images (CT, MRI, X-ray, ultrasound), anonymizing DICOM files, working with DICOM metadata and tags, converting DICOM images to other formats, handling compressed DICOM data, or processing medical imaging datasets. Applies to tasks involving medical image analysis, PACS systems, radiology workflows, and healthcare imaging applications.

15k tokens scripts
Remotion Best Practices
by ncklrs
×3

Best practices for Remotion - Video creation in React

19k tokens
Podcast Generation
by microsoft
vendor ×2

Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creation from content, or integrating with Azure OpenAI Realtime API for real audio output. Covers full-stack implementation from React frontend to Python FastAPI backend with WebSocket streaming.

4k tokens scripts
Remotion Best Practices
by ComeOnOliver
×2

Best practices for Remotion - Video creation in React

23k tokens
Remotion To Hyperframes
by aiskillstore
×1

Port an existing Remotion (React) composition''s source to HyperFrames HTML. Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source — one-way, Remotion-only. A passing Remotion mention, reference-only code, or "make something like my Remotion video" is a fresh build (/general-video). Unclear → /hyperframes.

88k tokens scripts
Gemini API Dev
by lingxling
×1

Use this skill when building applications with Gemini API hosted models, including Gemini and Gemma 4, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or needing current model specifications. Covers SDK usage...

2k tokens
Github Issue Creator
by lingxling
×1

Turn error logs, screenshots, voice notes, and rough bug reports into crisp, developer-ready GitHub issues with repro steps, impact, and evidence.

1k tokens

How to use it

Copy the folder

Take team-telnyx/telnyx-import-elevenlabs from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.