Sanity + Maintouch
Publish to Sanity as real Portable Text, mapped to your own schema.
Overview
Every Sanity project has its own schema, so there is no standard place for a body, a slug or a meta description. Pasting HTML into Portable Text loses tables, images and structure along the way.
Connect Sanity and map each document type’s fields once. Maintouch converts posts to Portable Text, uploads images to your Sanity assets and pushes title, slug, meta and schema fixes back to existing documents.
How it works
- 01
Add your API token
Paste your project ID, dataset and an API token. Maintouch then checks the project is ready to publish.
- 02
Map your document types
Pick the document types you publish and match each Maintouch field to a field in your schema.
- 03
Publish from Maintouch
Create new documents and update existing ones whenever a post changes.
What you get
Portable Text, not pasted HTML
Headings, lists, tables and images become Portable Text blocks your editors can work with in Studio.
Images in your asset library
Images are uploaded to Sanity assets and referenced from the document, not hotlinked.
Setup checks
See whether your GraphQL API is deployed and your Portable Text field allows tables and images, with the fix for anything missing.
Edits made in Sanity
Change a published document in Sanity and Maintouch pulls the new version back after your next site crawl.
Questions
Why do I need to deploy the GraphQL API?
Maintouch reads your fields from it to build the mapping. Run sanity graphql deploy in your Studio, and again after schema changes.
Which field can hold the post body?
A Portable Text field. Enable table and image blocks on it so those come through intact.
How are author fields filled?
Author references are matched to an existing document by name, so posts link to the authors you already have.
