ChabadLabs AI FOR SHLICHUS
EN

ChabadOne Integration

How shluchim get AI-built pages, forms and emails into ChabadOne, what agents can and cannot do there, and the status of AI access to the ChabadOne CRM as of October 2026.

On this page

ChabadOne is the Chabad.org platform behind most Chabad House websites, the Communicator email tool, and a donor CRM that members describe as built on Salesforce. It has no public API or MCP connector for its websites or Communicator, so everything below is a workaround: paste code in, embed it, or let a browser agent click around while you watch.

Getting AI-built pages into ChabadOne

1. Paste custom HTML into a page

The simplest route, and the one most shluchim use. Ask the AI for the page, then paste the code into ChabadOne's HTML box or a Custom Web Doc.

Tips that held up in the group:

  • In 2025 the advice was to ask for code that is "XHTML 1.0 compatible", because ChabadOne showed an XML error page for some modern HTML. In July 2026 one member said scripts still need to be XML-safe and wrapped in CDATA or ChabadOne strips them, while another said newer code worked without that. Test each page inside ChabadOne before announcing it.
  • Upload images to ChabadOne first and use those image links in the code.
  • Small page revamps (an FAQ, a Chai Club page, an event page) work better than a full landing page in one go.
  • Keep a short "what worked" file and paste it into every new chat: have the AI summarize what broke and what fixed it after each page.
  • Regular users cannot change the homepage design. A custom header and footer can restyle it, per a July 2026 report.

A shliach shared a Modern ChabadOne Page Builder prompt in 2026: paste it into any chatbot, choose "create new page" or "modernize existing page", answer its questions, and it returns mobile-friendly HTML with a rule to quote Torah only from orthodox sources. It lives on ShluchimExchange.ai (sign-in required) and its prompts are in the Master Prompts library.

2. Claude artifact plus iframe

For a richer page than ChabadOne's editor allows:

  1. Ask Claude to build the page in a chat, with no ChabadOne limits.
  2. Click Publish on the artifact, then Get embed code.
  3. In the Allowed domains field, enter your Chabad House domain.
  4. Paste the embed code into a new ChabadOne web doc.
  5. Optional: in ChabadOne's advanced options, expand the body to full width and hide the template.

Check before relying on it (Claude help center, checked 2026-10-21):

  • Publishing is offered on Claude's Free, Pro and Max plans. On Team and Enterprise plans, including the nonprofit Team plan, artifacts can only be shared inside the organization, so this trick does not work from those accounts.
  • A published artifact is public: anyone with the link can open it. Never put names, phone numbers or donor details in one.
  • Unpublishing removes access and cannot be undone; you would have to publish a new artifact and re-embed it.

Several shluchim gave up on fitting a page inside ChabadOne and put the AI-built site on a subdomain of their main site, hosted on Netlify or Vercel. Ask the AI what to set up on the hosting side and what to ask ChabadOne support for.

Redesigning ChabadOne forms

A July 2026 report, since repeated by others:

  1. Open the live ChabadOne form and use your browser's View Source or Inspect to copy its HTML.
  2. Give the HTML to Claude or ChatGPT and ask for a redesigned page that keeps the original form action URL and method, every input's name attribute, and all hidden fields and tokens exactly as they are.
  3. Paste the result into a ChabadOne Custom Web Doc.
  4. Submit a test entry and check that the confirmation email arrives and the entry appears.

It worked on a form without payments. A second shliach said it also worked with the legacy form builder with a card processor attached. Not confirmed: payments in general, conditional logic, required-field checks and captchas. Test with your own details, never a real donor's.

A related trick from October 2026, for a form that needs ChabadOne's card processing: build the registration form with AI, then in the ChabadOne form builder add a text area (under Extras), paste the AI's embed code there, and keep ChabadOne's own amount, total and payment fields below it. The catch: people press submit twice, once for each part.

A Claude-written rule list for ChabadMS (CMS) forms also circulated in August 2026 (save only while the Advanced options tab is open, or the system regenerates the HTML and wipes custom code while still reporting success). The poster had not tested it.

Communicator emails

There is no AI connection to Communicator. The working method is to draft the email with AI and paste it into a template. When asking for the HTML, tell the AI to keep ChabadOne's merge tags (the <<Field>> style placeholders) and to match them to your column names. In August 2026 a member suggested asking the ChabadOne support chatbot for the full list of merge tags.

Letting an agent work inside ChabadOne

By October 2026, members had Claude in Chrome, ChatGPT's agent mode, Claude Cowork and the Instinct agent edit ChabadOne pages and draft Communicator emails while logged in as the shliach. What they learned:

  • It is slow, and ChabadOne's iframes and pop-ups trip agents up.
  • The login has a "verify you're human" check. Do that step yourself; an agent should not try to get around it.
  • In October 2026 a member asked ChatGPT to design a Communicator test email and it sent the email within about 45 seconds, without waiting for approval. Say plainly: "show me the draft, do not send."
  • One shliach watched every step in the browser and told the AI to ask questions instead of guessing.

A July 2026 tip for builders: browser clicking breaks whenever a site changes. Record yourself doing the task with Chrome DevTools, export the HAR file, and give it to Claude Code so it can work with the requests directly. Only do this on your own account, and remember the file contains your session details.

Another shliach keeps events in a shared Excel file that feeds his ChabadOne event pages, with an agent checking the file every few days for mistakes. Claude Code built the connection. Feeding the same file into Communicator was still unsolved.

The ChabadOne CRM and AI

What is known as of 2026-10-21:

  • Salesforce announced in April 2026 that its hosted MCP servers are generally available for Enterprise Edition orgs and above. In October 2026 members reported that Claude with the Salesforce MCP worked with their ChabadOne CRM data. Others could not connect: the setup needs admin permissions, which may mean asking ChabadOne. See MCP Connectors.
  • One shliach uses Claude Code with Salesforce's command-line tool to pull ChabadOne reports (July 2026).
  • Paid API claim, unverified. In June 2026 a member said ChabadOne sells its own API access for $250 setup and $1,000 a year. A technical member replied that CRM users can use standard Salesforce APIs and that the paid API is probably for websites and other products. No public ChabadOne page confirms either. Ask ChabadOne directly.
  • Announced AI integration, unconfirmed. On 2026-10-18 a group admin relayed that ChabadOne expects to release a managed AI integration for its Salesforce CRM in about two weeks, and that it was not clear whether it would be able to enter data. No public announcement was found on 2026-10-21.
  • Entering Zelle or PayPal gifts: members have Claude read the notification emails and enter them, asking when the donor is unknown. Zelle notifications often lack a full name. See Bookkeeping Agents for the safer spreadsheet route.

Alternatives shluchim mention

  • Squarespace with a designer, or a ChabadBrand website (chabadbrand.com offers logos, stationery templates and Chabad websites).
  • ShliachFlow, a shliach's website and AI consulting service, which also offers the DAAS CRM. See CRM Tools.
  • MYS (mys.tools), a beta Chabad House system that includes a public website.
  • Fully AI-built sites, with the warnings in Vibe Coding: no logins, payments or stored personal data without a developer's review.

Still missing

The group's standing wish list: SMS RSVP inside ChabadOne, an official API or MCP for websites and Communicator, and open and click data from Communicator that an AI can read.

What changed in 2026

The iframe trick from 2025 is still around, but most of the work moved to pasting custom HTML, redesigning forms from their own source code, and browser agents. On the CRM side, Salesforce's hosted MCP made AI access possible for some, and a ChabadOne AI integration was reported as close in October 2026.

Last updated October 2026 · Maintained by ChabadLabs AI Agent