"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."

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

"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."

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.

"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."

"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."

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.

"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)

"Use the photo from the summer demo folder as the hero image."

"Find something from our library that fits this section and put it on the right."

Attach a photo and say "use this as the header image". Cora adds it to your media library and inserts it, so it is there for next time too.

"Use the image at example.org/photo.jpg in the second section."

Cora copies it into your media library and points the page at your copy — never at somebody else's server, which could disappear or change under you.

"Generate a warm illustration of volunteers packing food boxes, landscape, in our brand colours."

"We have no photo for this section — draw an abstract background in green tones, portrait."

Generating costs AI credits, per image. Finding, attaching and linking do not. A request like "build the page with a hero and three section images" can mean four generations, so it is worth saying "use our library where you can" if you are watching the budget.

You can ask for the shape — square, landscape or portrait — and for higher render quality. Higher quality costs more credits, so ask for it only when you need it.

Generated images land in your media library like any other file, marked as AI generated, in a folder you can name. They are searchable and reusable afterwards, and served from your own domain.

Be specific. "A photo of a person" gives you something generic; subject, setting, composition, mood and colours give you something usable.

Not for logos, portraits of real people, or anything that has to be factually accurate. Use a real asset for those.

A prompt can occasionally be refused by the image provider. Rephrase it and ask again — nothing is broken.

If your AI credits run out mid-request, Cora tells you rather than failing silently.

"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."

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 whether a near-identical target audience already exists before creating another one, so you do not end up with five redundant groups. This is about avoiding duplicate audiences; it is unrelated to recipients. Duplicate recipients are handled separately and automatically: a campaign email sent to several target audiences always reaches each person exactly once.

She suggests a name and only saves once you have confirmed it.

"What depends on this audience? Will anything break if I narrow it?"

"Which mails go to this group?"

"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."

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.

Workflows work the same whether they sit inside a campaign or on their own, so you can ask for either.

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

"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."

"Duplicate this as a B variant and make that version much shorter and more urgent."

"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."

"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."

"Put this photo in the hero." — an image you attach can be published straight into your media library and inserted into the content, so it is reusable later.

"Read our about page at example.org and use it to write the intro."

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.

Point her at your media library before asking her to generate images.

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.

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

Workflows: automating what happens after someone acts — the automation canvas itself