From n8n workflow to client chat in under 20 minutes.

BotLatch runs beside n8n in your Docker environment. It keeps the production webhook on the server and gives the client site a public bot ID. Your Stripe purchase does not create a BotLatch.com account.

1. Start BotLatch

Copy .env.example to .env, set the required values, then run docker compose up -d. Open https://your-botlatch-host/setup on the installed instance.

2. Create the local owner account

The first registration on the installed instance becomes its only owner. Registration closes after that account is created, and returning owners use Sign in on that same instance.

3. Connect a bot

Create a client, add a bot, paste its production n8n Chat Trigger URL, and enter each allowed website origin exactly, including scheme and port.

4. Test the relay

Use the built-in test page. A successful reply proves that BotLatch can reach n8n without exposing the destination URL to the browser.

5. Install the widget

Copy the generated script tag into the client website. Test the exact production origin before handoff. Chat visitors do not create accounts, and their requests go to the customer-controlled BotLatch host rather than BotLatch.com.

Done means

• The client site can send and receive a complete message.
• The browser never receives the n8n webhook URL.
• An unapproved origin is rejected.
• The client report shows the test message and response time.

Before real traffic: back up both the BotLatch data directory and data-protection key directory. The database without its keys cannot decrypt saved webhook URLs.