#issues with whatsapp

1 messages · Page 1 of 1 (latest)

wheat dagger
#

i’m trying it out with whatsapp but stil failing to get my clawdbot to speak

stark eagleBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

wheat dagger
#

will it have issues if my telegram and whatsapp are both connected ?

sand impBOT
# wheat dagger i’m trying it out with whatsapp but stil failing to get my clawdbot to speak

Hey! 🦐 Happy to help with your WhatsApp setup!

A few quick questions to get to the bottom of this:

  1. What version are you running? (clawdbot --version) - Version mismatches are the #1 cause of weird issues!

  2. Is the bot receiving messages but not replying, or not receiving at all?

  3. Have you linked WhatsApp successfully? (You should see it in clawdbot channels list)

Common culprits for the "not speaking" issue:

  • No model configured - Check clawdbot model list and clawdbot model use <model>
  • Out of credits on your model provider
  • Speaking disabled for the WhatsApp channel
  • Wrong channel config - WhatsApp needs to be set as both source AND target

The WhatsApp setup docs might help: https://docs.clawd.bot/channels/whatsapp

#

Let me know your version and we can dig deeper! 🦐

wheat dagger
#

still getting the http401 invalid bearer token?

sand impBOT
# wheat dagger

Found it! 🦐 The issue is not WhatsApp — it's your Anthropic API key:

Claude: HTTP 401: Invalid bearer token

Your WhatsApp is set up correctly (linked, enabled), but the bot can't reach Claude because the API key is invalid or missing.

To fix:

  1. Check your current Anthropic config:

    clawdbot auth list

  2. Add/update your Anthropic key:

# 
   clawdbot auth add anthropic

(or clawdbot auth update anthropic if you already have one set)

  1. Verify it's working:
    clawdbot model list

Make sure you're using a valid Anthropic API key from https://console.anthropic.com/ — the 401 means "Unauthorized," so either the key is wrong or the account has billing issues.

Let me know once you've updated the key and we can test it! 🦐

sand impBOT
# 
clawdbot gateway restart

After restart, try sending a message again. The 401 should go away once you have a valid Anthropic API key in place.

What does auth list show you?

nimble ruin
#

Whatsapp doesn't like bots and can get your account banned. They were discussing it on the voice call tonight

sand impBOT
# nimble ruin Whatsapp doesn't like bots and can get your account banned. They were discussing...

Oh! That's a good catch from Enoch! 🦐

Yes, this is real — WhatsApp is notoriously strict about automation. Their Terms of Service explicitly prohibit:

  • Bot-like automated messaging
  • Bulk messaging
  • Unauthenticated API usage

Risk of account bans is real — especially if:

  • You're sending messages too quickly/frequently
  • Using unofficial/unofficial methods
  • Getting reported by contacts

If you want to stay safer:

  • Slower message rates
  • Keep chats natural (not obvious bot behavior)
  • Consider using Telegram instead (much more bot-friendly, no ban risk)
#

That said — if you're just testing locally with friends/family who know it's a bot, many people use WhatsApp without issues. It's a calculated risk!

Back to your immediate issue: The 401 error is still the API key problem. If you want to proceed with WhatsApp, fix the Anthropic key first and we can go from there.

No judgment either way — just wanted you to have the full picture! 🦐

strange cobalt
#

i'm having an issue and this commend says returns "error: unkonwn command 'auth'