>- Import Vapi voice assistants into Telnyx with all configurations — instructions, greeting, voice settings, tools, and call analysis. Supports selective import by assistant ID and covers all SDK languages.
npx skills add https://github.com/team-telnyx/ai --skill telnyx-import-vapi
Migrate your Vapi voice assistants to Telnyx in minutes. The import API pulls assistant configurations directly from Vapi using your API key and recreates them as Telnyx AI Assistants.
Interaction model: Collect the user's Telnyx API key and Vapi API key, store the Vapi 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.
| Component | Imported? | Notes |
|-----------|-----------|-------|
| Instructions | Yes | Imported as-is |
| Greeting / first message | Yes | Maps to assistant greeting |
| Voice configuration | Yes | Voice provider and voice ID 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 |
Before importing, store your Vapi API key as an integration secret in Telnyx. Note the secret reference name (e.g., vapi_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.
Import every assistant from your Vapi account:
curl \
-X POST \
-H "Authorization: Bearer $TELNYX_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"provider": "vapi",
"api_key_ref": "vapi_api_key"
}' \
"https://api.telnyx.com/v2/ai/assistants/import"
import os
from telnyx import Telnyx
client = Telnyx(api_key=os.environ.get("TELNYX_API_KEY"))
assistants = client.ai.assistants.imports(
provider="vapi",
api_key_ref="vapi_api_key",
)
for assistant in assistants.data:
print(f"Imported: {assistant.name} (ID: {assistant.id})")
import Telnyx from 'telnyx';
const client = new Telnyx();
const assistants = await client.ai.assistants.imports({
provider: 'vapi',
api_key_ref: 'vapi_api_key',
});
for (const assistant of assistants.data) {
console.log(`Imported: ${assistant.name} (ID: ${assistant.id})`);
}
assistants, err := client.AI.Assistants.Imports(context.TODO(), telnyx.AIAssistantImportsParams{
Provider: telnyx.AIAssistantImportsParamsProviderVapi,
APIKeyRef: "vapi_api_key",
})
if err != nil {
panic(err.Error())
}
for _, a := range assistants.Data {
fmt.Printf("Imported: %s (ID: %s)\n", a.Name, a.ID)
}
import com.telnyx.sdk.models.ai.assistants.AssistantImportsParams;
import com.telnyx.sdk.models.ai.assistants.AssistantsList;
AssistantImportsParams params = AssistantImportsParams.builder()
.provider(AssistantImportsParams.Provider.VAPI)
.apiKeyRef("vapi_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()));
assistants = client.ai.assistants.imports(
provider: :vapi,
api_key_ref: "vapi_api_key"
)
assistants.data.each do |a|
puts "Imported: #{a.name} (ID: #{a.id})"
end
To import only certain assistants, pass their Vapi assistant IDs in import_ids:
curl \
-X POST \
-H "Authorization: Bearer $TELNYX_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"provider": "vapi",
"api_key_ref": "vapi_api_key",
"import_ids": ["vapi-assistant-id-1", "vapi-assistant-id-2"]
}' \
"https://api.telnyx.com/v2/ai/assistants/import"
assistants = client.ai.assistants.imports(
provider="vapi",
api_key_ref="vapi_api_key",
import_ids=["vapi-assistant-id-1", "vapi-assistant-id-2"],
)
const assistants = await client.ai.assistants.imports({
provider: 'vapi',
api_key_ref: 'vapi_api_key',
import_ids: ['vapi-assistant-id-1', 'vapi-assistant-id-2'],
});
List your Telnyx assistants to confirm the import succeeded:
curl -H "Authorization: Bearer $TELNYX_API_KEY" \
"https://api.telnyx.com/v2/ai/assistants"
assistants = client.ai.assistants.list()
for a in assistants.data:
print(f"{a.name} — {a.id} — imported: {a.import_metadata}")
const assistants = await client.ai.assistants.list();
for (const a of assistants.data) {
console.log(`${a.name} — ${a.id} — imported:`, a.import_metadata);
}
After importing, complete these manual steps:
Running the import again for the same Vapi assistants will overwrite the existing Telnyx copies with the latest configuration from Vapi. This is useful for syncing changes during a gradual migration.
| Field | Type | Required | Description |
|-------|------|----------|-------------|
| provider | string | Yes | Must be "vapi" |
| api_key_ref | string | Yes | Name of the Telnyx integration secret containing your Vapi API key |
| import_ids | array[string] | No | Specific Vapi assistant 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
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.
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.
Best practices for Remotion - Video creation in React
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.
Best practices for Remotion - Video creation in React
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.
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...
Turn error logs, screenshots, voice notes, and rough bug reports into crisp, developer-ready GitHub issues with repro steps, impact, and evidence.
Take team-telnyx/telnyx-import-vapi from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.