Arkweaver + Strapi integration
Arkweaver drafts blog posts from what customers said on calls and publishes them into your Strapi CMS, with the slug and meta description already filled in.
What syncs between Arkweaver and Strapi
- Arkweaver writes the post from the customer calls it has already read, so the quotes and examples in it are real.
- Arkweaver creates the entry in the Strapi collection you name, which defaults to blog-posts.
- Arkweaver writes the title, slug, excerpt and body into your own field names, which you can map if your content model differs.
- The slug is built from the deliverable and the feature it covers, and the excerpt uses the post’s own meta description.
- Each deliverable publishes as a draft or straight to live, and drafts wait for an editor.
- Republishing updates the entry Arkweaver created rather than adding a second one.
How to connect Strapi to Arkweaver
- Go to Settings, then Group Settings, then the Integrations tab, and add the Strapi integration.
- Enter your Strapi URL and an API token, plus your public blog URL so published posts link to the reader-facing page.
- Name the collection to publish into if it is not blog-posts, and map the Title, Slug, Excerpt and Content fields if your content model names them differently.
- Arkweaver tests the URL, token and collection together before saving, so a wrong value shows up at setup.
- Go to Settings, then Deliverables, and choose which deliverables publish to the blog and whether each one lands as a draft or goes live.
What you can do once connected
- Publish a launch post built from real customer language instead of starting a blank page after every ship.
- Keep an editor in the loop by letting posts land as drafts until someone approves them.
- Give search and answer engines a written meta description and a readable slug without anyone filling them in by hand.
- Update a published post in place when the deliverable is regenerated, rather than accumulating duplicates.
Frequently asked questions
Where does the content of these posts come from?
From the calls Arkweaver already reads. The post is written from what customers said about the feature, so the quotes and examples in it come from real conversations rather than being invented for a launch.
Do posts go live automatically?
Only if you choose that. Each deliverable is set to publish as a draft or to go live, and drafts sit in Strapi until an editor publishes them.
What if our collection uses different field names?
Map them once during setup. The Title, Slug, Excerpt and Content fields are all configurable, and the collection name defaults to blog-posts.
What happens when a deliverable is republished?
Arkweaver updates the entry it created rather than adding a duplicate. If that entry has since been deleted in Strapi, it creates a fresh one.