10 replies

Receiving files in telegram from clawdbot

✅Solved

I do not receive files from reports that Claws creates.

I checked on the doc and couldn’t see anything.

Also sometimes the messages are super slow. Like they take up to 5 minutes.
What could cause that?

Clawbot log:
I'm using Clawdbot (v2026.1.20-2, macOS, Telegram channel) and trying to send audio files to myself via the message tool:

{
"action": "send",
"target": "<my_chat_id>",
"message": "Daily summary",
"filePath": "/tmp/audio.mp3",
"asVoice": true
}

The message appears in Telegram with the caption and shows as a voice message, but it won't play (0:00 duration, no audio). The MP3 file plays fine locally (3 min, 1.4MB, 44.1kHz mono, 128kbps).

Is there a specific format requirement for Telegram voice messages via Clawdbot? (e.g., OGG/Opus instead of MP3?) Or is outbound file/voice sending not fully supported yet?

Running: clawdbot v2026.1.20-2 on macOS arm64, node v25.4.0

Solution

Hey! Let me help you troubleshoot all three issues:

1. Files from reports not being received

Agent replies with file attachments need to include a


```
Here's your report!
MEDIA:/path/to/file.pdf
```
The


```
Here's your report!
MEDIA:/path/to/file.pdf
```
The

message

 tool uses

 tool uses

media

 parameter instead of

 parameter instead of

filePath

. Make sure you're using the correct format.
## 2. Slow messages (up to 5 minutes)
This is likely the **IPv6 issue** mentioned in the Telegram docs. Some hosts resolve

. Make sure you're using the correct format.
## 2. Slow messages (up to 5 minutes)
This is likely the **IPv6 issue** mentioned in the Telegram docs. Some hosts resolve

api.telegram.org

 to IPv6 first, and if your server doesn't have working IPv6 egress, grammY gets stuck.
**Quick fix:** Force IPv4 for Telegram API by adding to

 to IPv6 first, and if your server doesn't have working IPv6 egress, grammY gets stuck.
**Quick fix:** Force IPv4 for Telegram API by adding to

/etc/hosts`:

149.154.167.220 api.telegram.org

149.154.167.220 api.telegram.org

Then restart the gateway. You can verify with:

bash

bash

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•3w ago•

10 replies

antoinersx

Receiving files in telegram from clawdbot

✅Solved

Solution

Hey! Let me help you troubleshoot all three issues:

1. Files from reports not being received

Agent replies with file attachments need to include a


```
Here's your report!
MEDIA:/path/to/file.pdf
```
The


```
Here's your report!
MEDIA:/path/to/file.pdf
```
The

message

 tool uses

 tool uses

media

 parameter instead of

 parameter instead of

filePath

. Make sure you're using the correct format.
## 2. Slow messages (up to 5 minutes)
This is likely the **IPv6 issue** mentioned in the Telegram docs. Some hosts resolve

. Make sure you're using the correct format.
## 2. Slow messages (up to 5 minutes)
This is likely the **IPv6 issue** mentioned in the Telegram docs. Some hosts resolve

api.telegram.org

 to IPv6 first, and if your server doesn't have working IPv6 egress, grammY gets stuck.
**Quick fix:** Force IPv4 for Telegram API by adding to

 to IPv6 first, and if your server doesn't have working IPv6 egress, grammY gets stuck.
**Quick fix:** Force IPv4 for Telegram API by adding to

/etc/hosts`:

149.154.167.220 api.telegram.org

149.154.167.220 api.telegram.org

Then restart the gateway. You can verify with:

bash

bash

Jump to solution

Receiving files in telegram from clawdbot

1. Files from reports not being received

Receiving files in telegram from clawdbot

1. Files from reports not being received

Similar Threads

Similar Threads

Similar Threads