Installation

Installation is a normal WordPress plugin upload followed by a four-step wizard. The wizard does the Cloudflare work for you; you will not need to open the Cloudflare dashboard except to create one API token.

Before you start

Have a Cloudflare account ready, and know which account you want the chatbot's resources created in if you have more than one. If your site is large, be aware that the first content index runs in the background over WP-Cron and can take a while. That is normal, and the wizard shows progress.

If you can, run through setup on a staging copy first. Setup is idempotent and safe to re-run, but a staging pass lets you see the wizard, the indexing behaviour and the widget without a live audience.

Step 1: Install the plugin

1. Log in to your WordPress dashboard.
2. Go to Plugins > Add New Plugin.
3. Click Upload Plugin, choose the zip file, and click Install Now.
4. Click Activate Plugin.

After activation a Flarepipe Chat item appears in the admin menu. Before setup is complete it opens the wizard; afterwards it opens the settings screen.

Step 2: Create and paste a setup token

The wizard links you straight to the Cloudflare token creation screen and lists the permissions to tick. The full list, and the reasoning behind each one, is on the Cloudflare setup page.

Paste the token into the wizard. If the token has access to more than one Cloudflare account, the wizard will ask you which one to use. If you want the bot served from your own subdomain rather than a workers.dev URL, fill in the custom domain field now. You can also do it later from settings.

Leave Delete the setup token from Cloudflare when finished ticked unless you are deliberately reusing the same token to set up several sites. It is checked by default for a reason.

Step 3: Let it provision

The wizard now runs four steps and reports each one:

1. Verify token and account. Confirms the token works and resolves which Cloudflare account to build in.
2. Deploy worker and vector index. Creates the Vectorize index, ensures your workers.dev subdomain exists, uploads the Worker with its bindings, and generates the shared secret used to protect content ingestion.
3. Downgrade to a minimal token. Mints a replacement token limited to redeploying the Worker and updating the index, stores it encrypted, then deletes the setup token if you asked it to.
4. Index your content. Queues your published posts and pages for chunking and embedding, working through them in small batches.

If a step fails, fix the cause and run setup again. Every operation treats "this already exists" as success, so re-running repairs a partial install rather than creating duplicates.

Step 4: Check it works

1. Open the front end of your site. The chat button should appear in the corner you configured.
2. Ask it something your site definitely covers. You should get a streamed answer with a link to the source page.
3. Ask it something your site definitely does not cover. It should decline rather than invent an answer.
4. Back in Flarepipe Chat > Settings, use Run diagnostics to confirm the Worker and its bindings are healthy.

Updating and uninstalling

Plugin updates may ship a new Worker version; the plugin holds a token scoped to redeploy the Worker so this happens without you re-entering credentials.

Uninstalling removes the plugin's own options, knowledge entries and post meta. It deliberately leaves your Cloudflare resources (the Worker, the index) alone, so nothing you built on disappears because a plugin was deleted. Remove those from the Cloudflare dashboard yourself if you want them gone.