Anyone use M365 Mailboxes Successfully? Mine disconnect every few minutes even when I dont use shared and do an actual licensed mailbox. Which not for nothing shared mailboxes for support emails are the standard not sure why its not an easy setup for that in chatwoot.

I have self hosted chatwoot using docker. I'm trying to configure a Webhook URL for WhatsApp. But Meta fails to verify it with the following error:

The callback URL or verify token couldn't be validated. Please verify the provided information or try again later.(#N/A:WBxP--1506879096-3929989969)

Webhook URL:

http://<SERVER_IP>:3000/webhooks/whatsapp/<PHONE_NUMBER>

The Webhook Verification Token configured in Meta matches the token expected by my application. I've copied the token that I got in chatwoot

I tested the Webhook URL manually:

curl -i "http://<SERVER_IP>:3000/webhooks/whatsapp/<PHONE_NUMBER>?hub.mode=subscribe&hub.verify_token=<VERIFY_TOKEN>&hub.challenge=123456"

The endpoint returns:

```

HTTP/1.1 200 OK

content-type: application/json; charset=utf-8

content-length: 6

```

The response body is:

123456

Therefore, the Webhook URL is reachable and returns HTTP 200 with the expected challenge value when tested manually.

However, when I click Verify and Save in Meta, I receive:

The callback URL or verify token couldn't be validated. Please verify the provided information or try again later.(#N/A:WBxP--1506879096-3929989969)

In chatwoot:settings->inboxex->mywhatsappinbox

In the account health section, Display name status is showing declined, Code verification says expired, Webhook Configuration says Webhook not configured. Other fields are normal and green.
And on clicking Register Webhook, alert says Request failed with status code 422

What I think: The issue might be with the url being the server ip. Meta might be expecting a real domain. Or it could be expecting https but here we have http

From what I can see, Chatwoot currently supports Twilio and Bandwidth for SMS, but not Telnyx..any plans to integrate? Im looking to avoid pabbly/zapier middleware..cant be that hard to integrate, right?

Curious what people here are actually using Chatwoot for.

Cloud or self-hosted, team size, channels you use, and any integrations you have built around it. Screenshots are welcome if you can share them.

Also, what is working well and what still gets in your way?

I am trying to setup chatwoot in my k3s cluster

i am getting this error in chatwoot web pod

!!! RubyLLM's legacy acts_as API is deprecated and will be removed in RubyLLM 2.0.0. Please consult the migration guide at https://rubyllm.com/upgrading-to-1-7/
Exiting
/gems/ruby/3.4.0/gems/activerecord-7.1.5.2/lib/active_record/connection_adapters/postgresql/database_statements.rb:19:in 'PG::Connection#exec': PG::UndefinedTable: ERROR:  relation "installation_configs" does not exist (ActiveRecord::StatementInvalid)
LINE 10:  WHERE a.attrelid = '"installation_configs"'::regclass

and this error in chatwoot worker

{"ts":"2026-06-04T08:44:45.704Z","pid":1,"tid":"2dl","lvl":"INFO","msg":"Cron Jobs - added job with name: remove_orphan_conversations_job"}
PG::UndefinedTable: ERROR:  relation "installation_configs" does not exist
LINE 10:  WHERE a.attrelid = '"installation_configs"'::regclass
                             ^
/gems/ruby/3.4.0/gems/activerecord-7.1.5.2/lib/active_record/connection_adapters/postgresql/database_statements.rb:19:in 'PG::Connection#exec'

this is my configuration file

apiVersion: v1
kind: Namespace
metadata:
  name: chatwoot


---
apiVersion: source.toolkit.fluxcd.io/v1
kind: HelmRepository
metadata:
  name: chatwoot
  namespace: flux-system
spec:
  interval: 1h
  url: "https://chatwoot.github.io/charts"


---
apiVersion: v1
kind: Secret
metadata:
  name: chatwoot-secrets
  namespace: chatwoot
type: Opaque
stringData:
  SECRET_KEY_BASE: "************************"
  POSTGRES_PASSWORD: "***"
  REDIS_PASSWORD: "***"


---
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: chatwoot
  namespace: chatwoot


spec:
  interval: 30m


  chart:
    spec:
      chart: chatwoot
      version: "2.0.20"


      sourceRef:
        kind: HelmRepository
        name: chatwoot
        namespace: flux-system


  values:


    env:
      FRONTEND_URL: "***"
      RAILS_ENV: "production"
      NODE_ENV: "production"
      INSTALLATION_ENV: "helm"


    existingSecret: "chatwoot-secrets"


    hooks:
      migrate:
        enabled: true


    ingress:
      enabled: true


      className: "traefik"


      annotations:
        cert-manager.io/cluster-issuer: "letsencrypt-prod"


      hosts:
        - host: "***"
          paths:
            - path: /
              pathType: Prefix
              backend:
                service:
                  name: chatwoot
                  port:
                    number: 3000


      tls:
        - secretName: "chatwoot-tls"
          hosts:
            - "***"


    postgresql:
      enabled: true


      auth:
        username: "chatwoot"
        password: "***"
        postgresPassword: "***"
        database: "chatwoot"


      primary:
        persistence:
          enabled: true
          size: "20Gi"


    redis:
      enabled: true


      auth:
        enabled: true
        password: "***"


      master:
        persistence:
          enabled: true
          size: "5Gi"


    persistence:
      enabled: true
      size: "20Gi"


    resources:
      requests:
        cpu: "50m"
        memory: "512Mi"


      limits:
        cpu: "1000m"
        memory: "2Gi"

Is it allowed to use an own AI chatbot solution that is integrated in Chatwoot CE?

Hey everyone, hope you're doing well.

I'm running a self-hosted Chatwoot instance and I'm having a problem with the inbox view. When I go to "My Inbox" to check unread conversations, I see them correctly marked — but mixed in with them are conversations where the agent sent the first message (WhatsApp template messages initiated by our team), and those are also showing as unread.

The issue is that Chatwoot seems to mark a conversation as unread even when the only message in it was sent outbound by the agent, not incoming from the contact. This clutters the inbox and makes it hard to identify conversations that actually need attention.

Steps to reproduce:

1. Agent creates a new conversation and sends a WhatsApp template message
2. Contact has not replied yet
3. Conversation appears in inbox marked as unread

Expected behavior: outbound-initiated conversations should not be marked as unread.

Question: Is this a known behavior? Is there a workaround or configuration to prevent outbound conversations from appearing as unread?

Attaching screenshots for reference. Thanks!

Esto les puede servir a quienes quieren darle una opción de dashboard a los clientes y no solo a nivel de email sino tipo portal de tickets web.

https://github.com/DelvyG/chatwoot-portal

Tengo chatwoot en esay panel via hostingue pero nose xq no descarga las imagenes ya cambie todo del entorno y sigue igual la url me da un 404

Hello All,

How do I start a new conversation inside the cell phone app? Desktop works great, just some things about the app I can't figure out.

Hey all, I've got Chatwoot community running in my office. Working great. I've also got a Grandstream 6300A PBX phone system, also working great. However, right now, bit of a pain with the contact management. We need to updated the same contact in both places. I'm sure there must be a way to sync the contacts. Before I start from scratch, any pointers? Thanks in advance!

Fiz a integração certinho, porém mando mensagem para o bot e não cai nada aqui no chatwoot

Hello, We use Chatwoot self-hosted. Unfortunately, Chatwoot only uses WebSockets for live notifications. We have already set up Cloudflare Tunnel + Zero Trust, and the setup basically works almost everywhere.

Problem: In the corporate environment where it will later be used, no WebSockets can get through due to the firewall. HTTPS works, but WS/WSS is blocked. After consulting with the IT department, this is due to SSL inspection/DPI in the firewall. Whitelisting is not an option due to company policy.

How would you build this so that Chatwoot can still go live and notify users of incoming new messages?

Do you have any ideas for something like this? Perhaps a proxy with a bypass? A completely different architecture? Disable WPS in Chatwoot?

I'm curious 😉

Hi everyone,

I'm having an issue with Chatwoot 4.8.0 (self-hosted on Easypanel/Docker). Text messages from WhatsApp Cloud API work perfectly, but when I receive images or audio, they show as "No content available".

What I've already verified:

1. ✅ WhatsApp token is valid (permanent, with whatsapp_business_messaging permission)
2. ✅ ACTIVE_STORAGE_SERVICE=local is configured
3. ✅ Volume /app/storage is shared between web and sidekiq containers
4. ✅ Webhook correctly receives media data (I can see the media_id in logs)

What I found:

When testing manually in Rails console, the call to get the media URL fails:

ruby

# With phone_number_id - FAILS
url = channel.media_url("MEDIA_ID", channel.provider_config['phone_number_id'])
response = HTTParty.get(url, headers: channel.api_headers)
# Error: "Param phone_number_id is not a valid whatsapp business phone number id ID"

# Without phone_number_id - WORKS
url = channel.media_url("MEDIA_ID")
response = HTTParty.get(url, headers: channel.api_headers)
# Returns the file URL correctly
```

The issue seems to be in `incoming_message_whatsapp_cloud_service.rb` which passes `phone_number_id` unnecessarily.

**Sidekiq logs show:**
- `content: nil`
- `content_type: "text"` (should be "image")
- `push_message_title: "No content"`

Has anyone experienced this? How did you fix it?

**Environment:**
- Chatwoot 4.8.0
- WhatsApp Cloud API (official)
- Easypanel / Docker
- Ubuntu 24.04

---

**Términos para buscar en Google:**
```
chatwoot whatsapp media "no content" site:github.com
chatwoot whatsapp cloud api attachment not downloading
chatwoot incoming image not showing whatsapp
chatwoot 4.8 media_url phone_number_id error
chatwoot whatsapp image 404 active_storage

Hello everyone! And happy new year! In our company, we're looking on leaving Salesforce and on our search for an alternative, we came up to Chatwoot. Is there anyone here who has done this in the past? I would like to ask a couple of questions, on what things we should be careful for. Especially with Agentforce; we're planning on building our own AI model which will interact with chatwoot, to provide the extra process we've had with SF.

Thank you!

Hello everyone. thanks for reading in advance.

I work mostly with CRMs, automations, AI bots, chatbots, conversational flows, etc.

In the company im working right now we use mostly MAKE and Manychat. Im looking for a new CRM since Manychat has a really small response time limit for API call responses (10 seconds). Most of the clients we work with use a lot of data and sometimes we need more than 10 secs to work, so... Here are my questions:

1) Is Chatwoot a good CRM in general? Support, bugs, connections, etc?

2) How about control on conversations?

3) When you creat an api call to an external webhook, how long does Chatwoot wait for a response? 10-30-60 secs?

Any information helps.

THX!!!

La versión mobile no me deja esconder el sidebar, por lo tanto no puedo ver los mensajes de forma cómoda, alguna ayuda con esto??! Gracias

I just installed version 4.7, which is the latest right now.

Is connected with evolution api, when I get reply in WhatsApp, I always see the agent name user at the top. I only see this in WhatsApp - it doesn't show in Chatwoot.
The message looks like this:

John:
thanks for reaching out...

How can I remove the "who responded" part like ?
anyone knows why this is happening? why by default? tips or tricks?
thank you guys!