Publishes to Sanity

Publish structured content into your Sanity dataset.

Articles are written into the dataset and document type you specify — as Portable Text, with the banner uploaded as a real image asset, not a URL string.

One project and three articles free. No card required.

What you connect

authorise once, publish from then on
01

Your project id and dataset

02

A token with write access

03

The document type articles should be created as

04

The API version to pin

What publishing to Sanity does

01

Portable Text, not an HTML dump

The article body lands as Portable Text blocks, so your front end renders it through the same components as everything else in the dataset.

02

Images as assets

The banner is uploaded to your project’s image assets and referenced from the document — resizable and queryable like any asset your team uploads.

03

Documents your schema owns

Each article is created as the document type you specify, carrying title, slug, excerpt, body and publish date. Republishing replaces the same document.

True of every integration

01

A full article, not a paste job

Each publish carries the title, slug, body, meta description, tags and the generated banner image. Nothing is reformatted by hand afterwards.

02

Republishing updates in place

The post’s id in your platform is stored on first publish. Publishing the article again updates that post instead of creating a duplicate.

03

Test before anything ships

Every connection has a test call that verifies the credentials against the platform before an article is ever sent. Your agent can run it too: test_integration.

04

A log per publish

Every attempt is recorded with its outcome. Failures can be retried without regenerating anything — retry_publish picks up the same article.

The shape of it

ConnectionSanity API
Body formatPortable Text
Banneruploaded as an asset
Setupabout two minutes
Start with three articles. Judge it by what ranks.

One project and three articles free. No card required.

Start free