Cora is the AI assistant built into CamBuildr. She does not just write text: she works inside your account, with your content, your theme, your tags, your audiences and your help articles.
This article is the complete tour of what Cora can do today, with concrete examples of what to ask for.
New to Cora? Start with Using Cora, the AI assistant in CamBuildr for the basics and prompt-writing tips, and Setting up AI in CamBuildr to switch AI on. This article assumes AI is already enabled.
Looking to drive CamBuildr from Claude, ChatGPT, VS Code Copilot or another external AI tool? That is a different feature — see Connecting CamBuildr to AI tools with MCP. The short version: Cora works inside CamBuildr, MCP lets an outside AI tool work on CamBuildr. There is a comparison at the end of this article.
Sections marked "Beta"
Some capabilities below are marked "Beta". These are features that are currently being tested, so they can be rough around the edges, but can enable you to do even more. They are switched off until you ask for them. Write to us in the chat bubble and we will enable them for your CamBuildr.
Where you meet Cora
Where | What she works on |
Landing page editor | The page you have open, all its blocks and settings |
Email editor | The mail you have open, subject line, preheader and the email's settings |
Target audience builder | The audience rules you are building |
Workflow editor | The automation graph you are building |
Campaign detail page | The whole campaign (Beta) |
Cora opens as a side panel next to what you are working on, so you can watch changes appear live. On narrow screens she opens as an overlay you can collapse.
1. Building and editing landing pages
Cora edits the actual page in the editor — sections, rows, columns, text, buttons, images, spacing and colours — not a copy you have to paste in yourself.
What to ask for
"Build a donation landing page for our winter emergency appeal: hero with a photo, three reasons to give, donation block with 25 / 50 / 100 € options, and a closing quote from a volunteer."
"The hero headline is too soft. Give me three punchier options and use the strongest one."
"Add a two-column section under the video: on the left the three key demands, on the right a signup form."
"Everything below the fold is too cramped — increase the spacing and make the section headings larger."
"Translate this page into French and keep the layout exactly as it is."
"Make the whole page match our brand colours."
Good to know
Cora reads your theme (colours, fonts, styles) automatically, so new sections come out on-brand without you describing the palette.
She works on the version you have open in the editor. Nothing is published until you save and publish as usual.
Cora can use the saved rows that you have if you ask for it
You can add system wide instructions through the Settings -> AI in the "Instructions" section
If Cora breaks something, you can use the "checkpoints" in the chat to go back to an earlier version, or you can also use the history to go back to an even earlier version of the landing page/email
2. Adding and configuring interactive blocks
This is the part that saves the most time. Cora can create and reconfigure CamBuildr's custom blocks — she fills in the block settings for you, not just the surrounding text.
If you give her a generic instruction like "please give me a landing page for an event", she might not know the intent, so you can include what is the goal of the landing page (or email) and you can also ask her for specific features to be included like "give me a landing page for a product launch. The main CTA is a signup form that asks for the email and name", this way she will know what to actually add.
What to ask for
"Add a signup form asking for first name, email and postcode. Postcode optional. Submit button: Count me in. Add a consent checkbox for the newsletter tag."
"Put a survey after the intro: one question, Which issue matters most to you?, with four answers — housing, transport, climate, safety."
"Add a donation block with 15 / 30 / 60 € and a monthly option, and set 30 € as the preselected amount."
"Add a countdown to 31 December 23:59 above the form."
"Add a progress bar showing signups towards our 10,000 target."
"Change the survey — drop the last answer option and make the question shorter."
Good to know
If a form needs a field you do not have yet, Cora can create the custom field for you. She can also create a new tag when a consent checkbox needs one.
For purchase blocks she can look up your connected Stripe products so the block points at a real product.
She reads the existing block's settings before changing them, so "just change the button text" does not reset the rest.
3. Page settings, SEO and sharing
Cora can also handle the settings around the content:
"Set the page title and social sharing text — something that works well when shared on WhatsApp."
"Rename this page to Winter Appeal 2027 and set the URL to
winter-appeal-2027.""Set the page language to German."
Renaming and URL changes affect the whole landing page (not just the variant you are editing), so Cora will ask for confirmation before doing it.
4. Writing and building emails
In the email editor Cora does everything she does on landing pages, plus the email-specific parts.
What to ask for
"Write a fundraising email to our monthly donors thanking them for last year and asking for a one-off winter gift. Warm, personal, under 250 words."
"Give me five subject lines for this mail and pick the one with the best open-rate chances. Then write a matching preheader."
"Add a share block at the bottom with Facebook, WhatsApp and email."
"Insert the recipient's first name in the greeting and fall back to Hi there when we do not have it."
"This is too long for mobile. Cut it to half without losing the ask."
"Add a one-question survey: Will you join us on the 14th? with Yes / No / Maybe."
Good to know
Cora can look up the placeholders available for this mail (first name, campaign fields, tracking links and so on) and insert the right ones instead of guessing.
Subject line and preheader are set through a small confirmation card so you always see what changes.
5. Working from your templates, using saved rows
Cora does not start from a blank page unless you want her to.
"Use our standard newsletter template as the starting point."
"Take the styling from the Spring Campaign template and apply it to this page."
"Insert our standard footer row." (once you have saved rows for this content type)
"Save this footer as a reusable row so we can drop it into other pages."
"Link to our Volunteer sign-up page in the second section." (she can list your existing pages and use the right link)
Cora can both use your saved rows and create them, so she can build a section once, save it for reuse, and insert it everywhere else.
Style extraction is useful when you like the look of an older asset but need entirely new content: Cora pulls out the fonts, colours and spacing, then builds fresh content with them.
6. Building target audiences
In the target audience builder Cora turns a plain-language description into actual filter rules and shows you the matching contact count before you save. Cora can check how everything is connected and also see a summary of the content, so you can ask in natural language, like "please give me the signups from all the landing pages about the workshop x" and she will know what to prepare.
What to ask for
"Everyone who signed up on one of our climate landing pages in the last 6 months but has not donated yet."
"Donors who gave more than 50 € last year, excluding anyone who unsubscribed."
"People who answered yes to the volunteering question in our summer survey and live in Berlin."
"How many people does that match? Now exclude everyone already in the Active volunteers audience."
Good to know
Cora looks up your real sources — your landing pages, mails, surveys, tags, products — so the rules point at things that actually exist.
She refreshes the preview count on request, so you can tune the rules until the size is right.
She checks for duplicates before creating another audience, so you do not end up with five near-identical groups.
She suggests a name and only saves once you have confirmed it.
Seeing how everything is wired together
Cora can read the dependency graph of your campaign: which pages feed which audiences, which audiences receive which mails, which actions fire which automations. Useful before you change something:
"What depends on this audience? Will anything break if I narrow it?"
"Which mails go to this group?"
7. Building workflows and automations
In the workflow editor Cora builds the automation graph: the start condition and the chain of actions, conditions and waits.
What to ask for
"When someone donates for the first time, send the thank-you mail immediately, wait 3 days, then send the what your gift does mail."
"Start this workflow when someone signs up on the Winter Appeal page."
"After the second mail, add a condition: if they clicked, tag them engaged, otherwise wait a week and send the reminder."
"Add a wait until 1 March before the last step."
Good to know
Cora reads the valid building blocks for your account first — your automated mails, tags, campaigns, person fields and action types — so she can only build a graph that actually works.
Structural changes are confirmed before they are saved: Cora shows you a validated preview, and only writes the new version once you approve.
8. Plan first: approve before Cora builds (Beta — contact us to enable)
For big requests, Cora can propose a written plan before touching anything: the purpose, the section-by-section outline, the tone, the call to action and the key decisions she has made. You get Approve and Reject buttons. Nothing is built until you approve.
Turn it on with the Plan first toggle in the chat, or just ask: "Plan it first, do not build yet."
This is worth using when:
You are building a whole page or mail from scratch
Several people need to agree on the direction first
The brief is broad and you want to catch misunderstandings before 20 sections exist
Start from a brief (Beta — contact us to enable)
With the same feature enabled, the landing page, campaign mail and target audience creation screens get a Customize with AI box. Type what you need, hit start, and Cora opens with the brief already in hand — she proposes the plan first, then builds it after your approval.
"A landing page for our March donor drive with a donation block, a supporter quote and a countdown to the 31st."
"An audience of everyone who came in through the climate petition but has never donated."
Try a variant without risking the original (Beta — contact us to enable)
"Duplicate this as a B variant and make that version much shorter and more urgent."
Cora copies the current variant into a new A/B variant and continues working on the copy. The original stays exactly as it was. (Requires a plan that includes A/B testing.)
9. Campaign conductor: plan a whole campaign (Beta — contact us to enable)
On a campaign page, Cora can act as a campaign conductor. Give her the brief for the entire campaign and she proposes a plan: the goal, the audience, the tone of voice, the primary call to action, the key messages — and the list of assets to create, each with its own short brief.
What to ask for
"We are running a three-week campaign to stop the demolition of the community centre. Goal: 5,000 petition signatures and 200 donors. Plan the landing pages, emails and follow-up automation."
You can edit the plan before approving it — rename assets, rewrite briefs, add or remove assets. When you approve, CamBuildr builds the assets for you in the background, several at a time, and the chat shows live progress ("4 of 7 ready"). Workflows are always built last, so the automated mails they send already exist. Cora also wires the pieces together — pointing a campaign mail at the right audience, setting the condition that fires a triggered mail.
When the build finishes, Cora reviews it against your brief and gives you one honest verdict: what matches the plan, what is missing and what does not fit. You get that summary instead of having to open every asset to find out.
Everything lands as a normal draft asset in your account, ready for you to review, refine and publish.
Working with Cora day to day
Attach files and screenshots
Drop an image, PDF, text, CSV, Markdown or JSON file (up to 10 MB) into the chat:
"Here is a screenshot of the design we agreed. Build the hero section like this."
"Here is our press release — turn it into a landing page."
"Use the copy in this document for the second section."
Checkpoints and undo
Before Cora makes a substantial content change she creates a checkpoint. If you do not like the result, click Restore checkpoint in the chat and the content goes back to how it was. A full rewrite always asks for confirmation first and always leaves a checkpoint behind.
Conversation history
Each piece of content keeps its own conversation, so you can pick up where you left off tomorrow. You can also delete a conversation to start fresh.
She reads the CamBuildr help centre
Cora can search and read CamBuildr's own help articles while she works, so she can answer questions like "how does the double opt-in flow affect this form?" using the real documentation instead of guessing.
She can read approved websites
If you list allowed domains in Settings > AI, Cora can pull in content from those sites:
"Read our about page at example.org and use it to write the intro."
Only domains you have explicitly approved are reachable.
Feedback
Thumbs up or thumbs down on any answer, with an optional comment. This feeds directly into improving Cora — negative feedback with a sentence about what went wrong is genuinely useful.
Stop a run
If Cora heads in the wrong direction, stop the response and re-prompt. You do not have to wait for her to finish.
Credits and limits
When Cora runs on CamBuildr's built-in AI key, usage is measured in AI credits and your plan includes a monthly quota. The chat shows how much you have used, and warns you when the quota is exhausted — at which point you can top up by contacting us. Credits do not apply when you connect your own OpenAI key in Settings > AI.
Cora or MCP — which one do I want?
| Cora (this article) | MCP (Connecting CamBuildr to AI tools with MCP) |
Where you work | Inside CamBuildr | Inside Claude, ChatGPT, VS Code Copilot, etc. |
Who it is for | Everyone in the team | Teams comfortable with AI tooling / developers |
Best at | Building and editing content in the editor, with live preview | Bulk and cross-tool work, looking up data, wiring CamBuildr into your own AI workflows |
Setup needed | Enable AI in Settings | Access token + connecting the external tool |
Typical use | "Build this landing page" | "List every landing page from Q4 and summarise their signup performance" |
They are not either/or: the MCP surface can hand a content job back to Cora, so an external tool can create a landing page and then ask Cora to write and build its content.
Good habits
Give the goal, the audience and the tone — not just "make it better".
One clear task per message; iterate in follow-ups.
Use Plan first for anything big.
Put evergreen brand rules into Settings > AI > Customer instructions, not into every prompt.
Treat everything as a draft: read it, check the facts, then publish.
Related articles
Using Cora, the AI assistant in CamBuildr — basics and prompt writing
Setting up AI in CamBuildr — enabling AI, API keys, customer instructions, allowed domains
Connecting CamBuildr to AI tools with MCP — using CamBuildr from external AI tools (Coming soon)