---
title: Deploy Chatwoot with AI
url: "/guides/chatwoot/"
canonical_url: https://docs.blossom88.com/guides/chatwoot/
markdown_url: https://docs.blossom88.com/guides/chatwoot.md
summary: Deploy Chatwoot with AI on Blossom. Add live chat to your website and give
  your team a shared support inbox, with PostgreSQL, Redis, and private R2 attachments.
categories:
- deployment
- support
---

# Deploy Chatwoot with AI

[Chatwoot](https://www.chatwoot.com/) gives your team a shared inbox for
customer conversations and a live-chat widget for your website. Visitors can
ask questions, send files, and continue the conversation with your team.

It uses a Ruby on Rails backend, a Vue frontend, and PostgreSQL. Browse the
[source on GitHub](https://github.com/chatwoot/chatwoot).

Run the web and background worker on regular App Capacity. Keep conversations
in PostgreSQL and attachments in your own private S3 or Cloudflare R2 bucket.

[Install the Blossom CLI and skill](/learn/getting-started/install/)
on your agent's machine and choose a Blossom Cloud Location when you log in.
You can also use
[Blossom BYOC (bring your own cloud)](/learn/getting-started/choose-your-cloud/#blossom-byoc).

## Ask Your Agent

> **Ask your AI agent:** Deploy Chatwoot on Blossom with R2 for attachments. Help me add live chat to my website.

> Follow this guide: https://docs.blossom88.com/guides/chatwoot/



Your agent checks the current
[Chatwoot deployment requirements](https://developers.chatwoot.com/self-hosted/deployment/docker),
selects compatible maintained releases, and saves the configuration.

| Part | Purpose |
|---|---|
| Web Service | Serves the support workspace, API, and website widget |
| Worker Service | Processes background jobs with Sidekiq |
| PostgreSQL with pgvector | Keeps accounts, contacts, conversations, and attachment records |
| Managed Redis | Coordinates background jobs and live updates |
| Your private bucket | Keeps uploaded attachments independently of Containers |

Use a private PostgreSQL image that includes Chatwoot's required extensions.
When the managed PostgreSQL image doesn't include `pgvector`, run it as a
[Persistent Service](/docs/apps/persistent-services/). Mount its
Volume directly at the image's data directory and start PostgreSQL first.
Keep its port private.

Run `bundle exec rails db:chatwoot_prepare` **once in the Release Phase**,
before starting the web and worker Services. Require it to succeed. Both
Services use the same compatible image, database, Redis connection, stable
`SECRET_KEY_BASE`, and canonical HTTPS `FRONTEND_URL`.

### Connect Your Bucket

Create a private bucket in your own provider account and a bucket-restricted
credential. Supply its endpoint, region, bucket, and credentials through a
private environment file. Keep provider administration credentials off the app.

Select Chatwoot's `s3_compatible` storage adapter for both Services. With R2,
use path-style requests and set `AWS_REQUEST_CHECKSUM_CALCULATION` to
`when_required` so the AWS SDK doesn't add a second checksum to Rails uploads. Check a real
upload and download before inviting your team.

### Create the Owner and Website Inbox

Keep the site behind **Blossom Account access** while creating its owner.
Open the generated HTTPS address and finish Chatwoot's setup. Disable public
account signup; use invitations for additional teammates.

Create a **Website** inbox, assign your team, and copy its widget snippet into
your website. Allow public access to the widget and its collection endpoints
so visitors can send messages. Chatwoot's own authentication protects the
support workspace.

Configure an email provider before relying on invitations, password resets,
or email support. Other channels need their own provider setup.

## Answer Your First Conversation

> **Ask your AI agent:** Help me send a test message from my website, reply from Chatwoot, and check a file attachment.

> Follow this guide: https://docs.blossom88.com/guides/chatwoot/



Open your website as a visitor and send a question. Reply from the support
inbox, then upload and download a sample file. Confirm that the reply reaches
the visitor and the downloaded file opens correctly.

![A website conversation and agent reply in Chatwoot running on Blossom.](/assets/images/guides/chatwoot/conversation.png)

<details class="optional-reading" markdown="1">
<summary>Commands behind the deployment</summary>

Create an App and prebuilt-image Environment using compatible images selected
by your agent:

    blossom app:create --data app.yml
    blossom environment:create --data environment.yml
    blossom service:create --data postgres-service.yml
    blossom cache_instance:create --data redis.yml --follow
    blossom environment_link:create --data redis-link.yml
    blossom env_var:push --environment environment-100 --file .env.production
    blossom environment:deploy --id environment-100 --follow

With PostgreSQL ready, create the web and worker Services. The web process
runs `bundle exec rails s -p 3000 -b 0.0.0.0` with an HTTP readiness check at
`/api`. The worker runs `bundle exec sidekiq -C config/sidekiq.yml`, without a
public port. Keep the same connection settings on both.

    blossom service:create --data web-service.yml
    blossom service:create --data worker-service.yml
    blossom environment:deploy_hooks:update --id environment-100 --data hooks.yml
    blossom environment:deploy --id environment-100 --follow

For a generated address, save the resulting canonical HTTPS URL as
`FRONTEND_URL` for both Services and redeploy before creating your workspace.
You can also use your final custom domain.

R2 storage variables:

```yaml
ACTIVE_STORAGE_SERVICE: s3_compatible
STORAGE_BUCKET_NAME: your-private-bucket
STORAGE_ENDPOINT: https://your-account.r2.cloudflarestorage.com
STORAGE_REGION: auto
STORAGE_FORCE_PATH_STYLE: "true"
AWS_REQUEST_CHECKSUM_CALCULATION: when_required
```

Supply `STORAGE_ACCESS_KEY_ID` and `STORAGE_SECRET_ACCESS_KEY` privately.
Use credentials with a lifetime suitable for your deployment.

</details>

## Keep Conversations Through Updates

> **Ask your AI agent:** Update Chatwoot and check that our conversations and attachments are still there.

> Follow this guide: https://docs.blossom88.com/guides/chatwoot/



Follow Chatwoot's supported upgrade path and let the Release Phase finish
before new processes start. Keep the database Volume, bucket, connection
settings, and application secret stable.

Web and worker Containers can be replaced without keeping their local disks.
The PostgreSQL Persistent Service has one active writer. Adding web Containers
doesn't make that database highly available; review Chatwoot's scaling
requirements before changing replica counts.

Configure database backups and bucket backups. For a PostgreSQL Persistent
Service, test a database-aware backup and restore; a Volume backup alone
doesn't establish application consistency.

## What You Get

- A support workspace at an HTTPS address
- Website live chat with a shared team inbox
- Separate web and worker Services with private PostgreSQL and managed Redis
- Attachments in your own private S3 or R2 bucket
