Ghost StrawberryDrafts that arrive with the sources already checked
Six references read, the two that hold up kept, tags and excerpt and meta description filled in, internal links in place. You open the editor and press publish.
The dull parts of running a publication take the day. Turning a long piece into a draft with the right tags and a meta description. Reading six sources and checking they say what the summary claimed. Finding the internal links that make the piece useful, and the ones now pointing at a slug you renamed eight months ago.
A companion does all of that in the browser and creates the post as a draft, using an Admin API key you authorise. Publishing stays with you, because Ghost merges publishing and email: when a post becomes published with email enabled, the newsletter goes to everyone immediately.
What is the safe version of this workflow?
Drafts only.
A companion researches, writes, formats and creates the post as a draft. You open the Ghost editor, read it, and press publish. That division keeps the part that saves the day: the writing, the formatting and the internal links.
If a status-changing action exists in the tool list, set it to Ask every time or switch it off in the Permissions block on the Ghost entry under `strawberry://settings/integrations`. The Available tools list on that page names every tool and marks the read-only ones.
What is worth doing with the connection?
The dull parts.
Turning a long piece into a draft with the right tags and a meta description. Auditing which of two hundred posts have no excerpt, no feature image or a tag never used again. Finding internal links pointing at a slug you renamed eight months ago.
A companion also handles the research half in the browser, which is where the actual work is: reading sources, checking a claim, pulling the numbers, then creating the draft with the citations in place. That is content repurposing and newsletter curation, and the marketing playbook covers the shape of it.
- Draft creation with tags, excerpt and meta description filled in.
- Post audits: missing excerpts, unused tags, internal links pointing at renamed slugs.
- Member and newsletter reads, where the tool list exposes them.
- Status changes: the one action that sends email, so treat it as consequential.
Admin API versus Content API
Ghost ships two.
The Content API is read-only and meant for a front end fetching published posts. The Admin API writes, sees drafts, and can read members. They are separate keys with very different authority, and they appear as separate connectable apps.
If you want a companion that reads your published posts, connect the read-only key and the publish-sends-email question never comes up. For draft creation, connect the admin key and keep status changes behind an approval.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents