Set up Help with your coding AI

Write your own code with Claude Code, Cursor, VS Code or Codex? Connect it to Help and it does the setting up for you: it puts the form on your pages, proves your domain, recognises your logged-in customers and builds the side panel your team sees beside each ticket. This works on every plan, Free included.

Steps

1. In the portal, open Sites, press Add a site and choose My own code.
2. On the site's Install tab, choose Let your coding AI do it, and connect your app (below). Your app opens a Help page in your browser: sign in, pick the workspace and approve, with Set up sites, forms, articles, domains, side panels and buttons on, and Create keys and secrets too if you want it to make the secrets.
3. Copy the words under Paste these words into your app's chat, in your project. They name your site and the order to work in.
4. Deploy when it asks, and send yourself a message from your site. It arrives in Tickets, and the Install tab ticks each step.

What the words ask for

In this order, because each step needs the one before it:

1. The install code (get_install_code): one script tag in the <head> of every page, the Help button before </body>, and the form on your contact or support page.
2. Your domain (add_domain): a <meta name="deltabreen-help"> tag in the home page's <head>, then, once deployed, verify_domain, and the live key in place of the test key.
3. Logged-in customers (create_login_secret): a short route on your server, GET /help-token, that answers the logged-in customer's token with our library, and data-help-identity-url="/help-token" on the script tag.
4. The side panel (create_integration): a route on your server, POST /support/hook, that answers with what your team should see about a customer. Once it is deployed on https: test_integration, get_integration_sample_shape and set_side_panel.
5. A last look (get_site_health): which pages opened your form, and why any was turned away, so your AI fixes it.

Our libraries do the signing and checking in those two routes, with no dependencies: help-server.mjs for Node, deltabreen_help.py for Python and deltabreen-help.php for PHP. See Logged-in users and Integrations.

Secrets

The two secrets, for logged-in customers and for your URL, go in your server's environment as HELP_IDENTITY_SECRET and HELP_CONNECTOR_SECRET, never in a page or a commit.

• With Create keys and secrets switched on, your AI makes each one and puts it there. The secret passes through your AI to do so, as anything it reads does.
• With it off, your AI stops at those steps and tells you. Make the secrets yourself on the site's Settings tab and on the integration's Connection tab, and put them in your environment.

Only the workspace's owner is offered that switch.

What depends on your plan

Setting up works on every plan, but each part keeps its plan's limits, as it does when you do it yourself: Free has one site, and integrations are on Lite and higher. When a step is outside your plan, your AI skips it and tells you which. Reading and answering tickets with your AI is on Pro and higher (Connect your own AI).

What we see from your site

The Install tab's What we see from your site, and get_site_health for your AI, list the last seven days: the pages that opened your form, with which key and as whom, and every page turned away, with why. A logged-in customer's token that didn't check out says what was wrong with it. We keep a word and the page's address, never a token or anything a visitor typed.