Sanity integration
Sanity keeps content as structured documents in a dataset you control. The Sanity integration reads and writes those documents, so WriteWorks fits your schema instead of asking you to bend it.
What the Sanity integration is
The Sanity connection works against a project and dataset you nominate, using a token you create. WriteWorks can create documents, update existing ones and read what is already there, which matters when a brief needs to know whether the page exists.
Because Sanity schemas differ from project to project, fields are mapped explicitly. Nothing is written to a field WriteWorks was not told about.
What you can do with it
Four questions the two data sets answer together that neither answers alone.
Documents are created against the type and fields you nominate, so what lands in the dataset is valid for the front end reading it.
WriteWorks can check what already exists, which is how it knows whether to improve a document or create one.
Point at production or a staging dataset, so content can be reviewed before it is live.
Once a document is live, its URL is tracked for citations and search performance and linked to the brief behind it.
How the Sanity integration works
About a minute to connect, and nothing to maintain afterwards.
Create a Sanity API token
In your Sanity project, create a token with write access to the dataset you want WriteWorks to use.
Connect it in WriteWorks
Open Settings, then Integrations, and choose Sanity. Add the token, project ID and dataset.
Map the document type
Choose which document type new work creates, and map the draft's parts to its fields.
Publish and track
Approved drafts become documents in your dataset, and published URLs are tracked from then on.
Who uses the Sanity integration
The same connection answers a different question depending on who is asking.
No import script to write or maintain, and nothing written outside the schema.
Draft and review in one place, then land in the dataset the site actually reads.
Stage into a separate dataset and promote when ready.
One token per client project, with datasets kept apart.
You bring your own account. The Sanity integration authenticates with your own account at Sanity, on your own plan and your own quota. WriteWorks reads the data that account already has access to, and nothing else. Disconnect at any time and the stored credential is deleted.
Works well alongside
Sanity integration FAQs
The questions teams ask before connecting it.
What does the Sanity integration do?+
What permissions does the token need?+
Does it work with custom schemas?+
How do I connect Sanity to WriteWorks?+
Can I publish to a staging dataset?+
What happens if I disconnect it?+
Connect Sanity and see the whole picture
Measure how 10+ AI platforms answer your buyers, join it to the paid and organic data you already have, and ship the content that flips the citation.