Authoring Content with Your Own AI Agent

Updated July 11, 2026

When you connect your own AI assistant (Claude or ChatGPT) to Marmend, it can do more than read data — it can create content for you: vacancies, candidate emails, and more. The key idea: your assistant writes the content, Marmend provides the rails.

Important for billing: content written by your connected assistant uses your assistant's subscription — it is not billed as Marmend AI usage. Marmend only validates, stores, and publishes what your assistant writes.

How it works

You: "Create a vacancy for a senior backend engineer in Berlin, hybrid, €80–100k"

Your assistant:
  1. Asks Marmend for the authoring guidelines (structure, allowed values, rules)
  2. Writes the full vacancy itself — description, requirements, salary details
  3. Submits the draft to Marmend
  4. Marmend validates it against the required structure and shows you a preview
  5. You confirm — the vacancy is saved as an unpublished draft in Marmend

Nothing goes live without your confirmation, and everything your assistant creates lands in Marmend exactly like content created in the app — same storage, same publishing flow, same team visibility.

What your assistant can create

Content	What happens in Marmend	Who can do it
Vacancies	Saved as an unpublished draft; publishing is a separate confirmed step. Include requirements — candidate matching depends on them.	Recruiters and above
Candidate emails	Wrapped in your company's email layout and branding, then sent through your connected email — after you confirm. A preview mode lets the assistant check an email without sending anything.	Recruiters and above
Documents & social posts	Saved as drafts in Marmend for review.	Recruiters and above
Website / CMS pages	Full management: list what exists, read a page, create, update, and publish. Content validated against your site's page structure; publishing changes the live site, so it always requires explicit confirmation.	Owners and administrators only
Marmend.com site pages — blog posts, integration guides, legal pages, product & solution pages, customer stories	Saved as drafts on the platform's own website; publishing puts them live on marmend.com and always asks for your confirmation first.	Marmend staff only (owners/administrators of the staff workspace)

Updating existing content

Your assistant can also replace the content of an existing vacancy — it reads the current version, rewrites it, and submits the full replacement for your confirmation. Anything your team added manually (like hand-picked requirements) is preserved.

The same works for your site's CMS pages: the assistant lists your pages, reads one, submits the replacement content, and — once you confirm — publishes the page again to push the change live. A live page's address (slug) can't be renamed directly: unpublish first, rename, then publish.

Managing the marmend.com website (Marmend staff)

If you are an owner or administrator of the Marmend staff workspace, your connected assistant can manage the entire content of the public marmend.com site — no deploy, no code:

Check what exists — list all pages (blog, integration guides, legal, product, solutions, customer stories) with their status: draft, published, or archived.
Read a page — fetch the full content of any page before editing or translating it.
Create a page — the assistant fetches the page structure, writes the content itself, and saves it as a draft. Each page type has its home: blog posts under /blog, integration guides under /integrations, legal pages under /legal, product pages under /product, solution pages under /solutions, customer stories under /customers.
Update a page — replace the title, body, or SEO fields. A live page keeps showing its old content until you publish again.
Publish or unpublish — publishing renders the page and puts it live on marmend.com; because this changes the public site, the assistant always asks you to confirm. Publishing again after an update pushes the new content live.

A typical session:

You: "Draft a blog post announcing the new Interview Intelligence features, then show me what we have in /product"

Your assistant:
  1. Lists the existing product pages
  2. Fetches the blog-post structure from Marmend
  3. Writes the post and saves it as a draft
  4. When you're happy: "Publish it" → you confirm → it's live at marmend.com/blog/…

Translations: ask the assistant to read the English page, translate it, and create the translation as a new page in the target language. Give the translation its own address (slug) before publishing — two languages can't be live at the same address, and Marmend will refuse the publish if you try.

One rule to know: the address (slug) of a live page can't be renamed directly — unpublish it first, rename, then publish again. This prevents stale copies of the page lingering at the old address.

The guardrails

Structure is enforced. Marmend rejects drafts that don't match the required structure and tells the assistant exactly what to fix — you'll rarely see this; the assistant corrects itself.
Nothing outward happens silently. Sending an email, publishing a vacancy, or changing a website page always requires your confirmation in the assistant.
Permissions follow your Marmend role. Your assistant can only create what you could create in the app. Company website pages are restricted to owners/administrators; marmend.com pages are restricted to the Marmend staff workspace — other workspaces never even see those tools.
Full history. Content created by an external assistant is marked as externally authored in the revision history, so you can always see who (or what) wrote something.

Tips for best results

Give your assistant a rich brief — seniority, must-have skills, location, work mode, salary range. It fills the structure from what you tell it and won't invent what you didn't say.
For vacancies, ask it to include a complete requirements list — that's what powers candidate matching in Marmend.
If the assistant says a field or value was rejected, just tell it to fetch the guidelines and fix the draft — it knows how.