Turn failed content checks into issues
Connect
SPIRITT
SanitySanity content.
Put structure to work.
SPIRITT queries your Sanity datasets, builds tools around your content, and carries editorial fixes into your team's workflow. It also maintains organization role assignments and user attributes within your access rules.
What you can do with Sanity.
Content you can trust
Find missing fields and unresolved references in Sanity documents, then coordinate repairs with evidence that editors can act on.
Interfaces for your content
Build searchable libraries and readiness dashboards around your document types, fields, and references without replacing Sanity.
Accountable access
Review resource users, roles, and service accounts, then apply authorized organization role changes and maintain user attributes.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your editorial operations, content tools, or Sanity access management.
02
Connect Sanity
Connect Sanity with an API key that has the access your mission needs, and identify the project and dataset to use.
03
Delegate an outcome
Ask SPIRITT to build a content explorer, run reference checks, or maintain organization access under your rules.
Hand over a mission.
Choose a mission. Make it yours.
Put Sanity to work.
Put your content operation to work
Questions
Sanity, with SPIRITT.
01What can SPIRITT do directly in Sanity?+
SPIRITT can query datasets with GROQ, retrieve documents by ID, inspect projects and access assignments, and send a one-shot prompt to Sanity Content Agent. It can also assign organization roles, create user attribute definitions, update user attribute values, and delete documents within the authorized scope.
02What access does the connection need?+
Sanity connects through an API key. SPIRITT can validate the credentials and use the projects, datasets, and organization resources that key permits. A content audit needs document access; an organization role maintenance mission also needs permission to make those role changes.
03Can it maintain a recurring editorial workflow?+
Yes. SPIRITT can run scheduled GROQ checks for required fields, reference integrity, or locale coverage, create work in connected task tools, and requery Sanity to verify repairs. Content editors can keep making their changes in Sanity while SPIRITT maintains the queue and checks the outcome.
04How does Sanity work with our other tools?+
Sanity document IDs and query results can become Linear issues, Asana localization tasks, Slack launch summaries, or Google Sheets migration inventories. SPIRITT can carry the source IDs and failed checks into each handoff so the work stays tied to the affected content.
05What can SPIRITT build around our dataset?+
It can build a private content explorer, release readiness dashboard, localization desk, or structured export workflow. Those tools can reflect your actual document types and reference relationships, using Sanity as the content source rather than requiring a second editorial database.
06Is this the same as using Sanity Content Agent?+
No. A one-shot Sanity Content Agent prompt is a self-contained request without an ongoing conversation thread. SPIRITT can also query documents independently, build interfaces, coordinate work in other tools, and verify outcomes. Document querying powers those checks; general document creation and field editing stay in your existing editorial workflow, rather than being direct actions through this integration.