# How to connect Teltel to OpenClaw (paste one key, 26 tools)

> Connect Teltel to OpenClaw with ClawLink: paste your Teltel key once and 26 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/openclaw/teltel

The usual route to Teltel access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Teltel setup: install one ClawHub skill, connect Teltel in the browser, and OpenClaw can call real Teltel actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect OpenClaw to Teltel.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Teltel** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask OpenClaw in plain English.

**Paste this into OpenClaw to set up ClawLink:**

> I want to connect my apps to OpenClaw through ClawLink.
> Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin`
> When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md

**Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect teltel  # connect Teltel (browser OAuth)
npx -y @useclawlink/cli actions teltel  # list available actions
npx -y @useclawlink/cli run teltel <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:

```bash
openclaw plugins install clawhub:clawlink-plugin
```

Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Teltel in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Teltel API key once.

Verify the connection by asking OpenClaw:

> Pull the relevant data from Teltel, summarize it in plain English, and point out anything that needs attention.

### Using a different agent?

The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once Teltel is connected in the dashboard, that agent calls the same 26 Teltel tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## Teltel MCP for OpenClaw

Looking for a Teltel MCP server for OpenClaw? ClawLink connects Teltel to OpenClaw and exposes 26 Teltel tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Teltel integration](https://claw-link.dev/hermes/teltel) works the same way.

## What the OpenClaw Teltel integration can do

26 Teltel tools are ready for OpenClaw once the account is connected. The 24 below are the ones people reach for most; your agent can call all 26.

### 24 of 26 Teltel tools for OpenClaw

| Tool | What it does |
|---|---|
| **Get account balance** `teltel_get_account_balance` | Retrieve the account balance for your TelTel account |
| **Get call list** `teltel_get_call_list` | Retrieve a list of calls with details (duration, time, status) |
| **Get country** `teltel_get_country` | Retrieve country resource information by ID from TelTel |
| **Get sms list** `teltel_get_sms_list` | Retrieve a list of sent (outbox) or received (inbox) SMS messages from TelTel |
| **Get user cid groups** `teltel_get_user_cid_groups` | Retrieve caller ID groups for a specific user |
| **Get users list** `teltel_get_users_list` | Retrieve a list of users from your TelTel account |
| **List auto dialers** `teltel_list_auto_dialers` | Retrieve a list of autodialer campaigns from TelTel |
| **List autodialer actions** `teltel_list_autodialer_actions` | Retrieve the action history for an autodialer campaign |
| **List autodialer contacts** `teltel_list_autodialer_contacts` | Retrieve the contact list for an autodialer campaign |
| **List autodialer custom statuses** `teltel_list_autodialer_custom_statuses` | Retrieve list of autodialer custom statuses |
| **List available countries** `teltel_list_available_countries` | Get the list of countries where DID numbers are available for purchase |
| **List country price groups** `teltel_list_country_price_groups` | Retrieve phone number price groups available in a specific country |
| **List devices** `teltel_list_devices` | Retrieve a list of devices from your TelTel account |
| **List my numbers** `teltel_list_my_numbers` | Retrieve a list of phone numbers (DIDs) owned by the account |
| **List orders** `teltel_list_orders` | Retrieve a list of DID (phone number) orders from TelTel |
| **List user statuses** `teltel_list_user_statuses` | Retrieve a list of all user statuses in TelTel |
| **Lookup phone number** `teltel_lookup_phone_number` | Perform HLR (Home Location Register) lookup for phone numbers via TelTel API |
| **Receive inbound sms** `teltel_receive_inbound_sms` | Process inbound SMS webhook data from TelTel |
| **Create autodialer custom status** `teltel_create_autodialer_custom_status` | Create a custom status for autodialer contacts |
| **Create call** `teltel_create_call` | Create a call between two participants |
| **Create user status** `teltel_create_user_status` | Create a user status in TelTel |
| **Set user status** `teltel_set_user_status` | Set a user's status in TelTel |
| **Update autodialer custom status** `teltel_update_autodialer_custom_status` | Update an autodialer custom status value by ID |
| **Update user status** `teltel_update_user_status` | Update an existing user status in TelTel |

## Example prompts

**Get Account Balance**

> Pull the relevant data from Teltel, summarize it in plain English, and point out anything that needs attention.

**Get Call List**

> Pull the relevant data from Teltel, summarize it in plain English, and point out anything that needs attention.

**Get Country**

> Pull the relevant data from Teltel, summarize it in plain English, and point out anything that needs attention.

**Get Sms List**

> Pull the relevant data from Teltel, summarize it in plain English, and point out anything that needs attention.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Teltel working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Teltel API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Teltel account becomes available to the agent without you building credential management. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Teltel. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| **Agent usability** | You still need to expose the right Teltel actions to the runtime in a format your agent can reliably use. | 26 tools for Teltel are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Teltel to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Teltel in the browser, and the 26 tools above work from chat. There is no SDK and no config file, and the Teltel key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### OpenClaw installed the Teltel skill but can't call the tools
The ClawHub skill teaches OpenClaw about Teltel, but the calls run through the ClawLink plugin and your connected account. Make sure Teltel is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

### Connection succeeds but no tools appear
Reconnect Teltel from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

### "Tool schema not loaded yet" error when calling Teltel tools
Teltel tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Teltel call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

### Teltel returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

### API key setup works but results look incomplete
Double-check that the API key for Teltel has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Teltel integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Teltel: link your Teltel account once in the browser and OpenClaw can call the Teltel API through 26 ready-made tools — no custom code or token handling.

### How do I add Teltel to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Teltel skill from ClawHub, then you click Connect in the dashboard to authorize Teltel. OpenClaw calls the tools from the next message — no config files, and the Teltel key you paste is stored server-side instead of in your environment.

### How long does it take to connect Teltel to OpenClaw?
About two minutes. Sign in, click Connect next to Teltel in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Teltel up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Teltel working from chat.

### OpenClaw installed the Teltel skill but can't call the tools
The ClawHub skill teaches OpenClaw about Teltel, but the calls run through the ClawLink plugin and your connected account. Make sure Teltel is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

## Related

- [OpenClaw SendGrid integration](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails
- [Dialpad](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing
- [OpenClaw Discord Bot integration](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions
