Flag docs edited after export
Connect
SPIRITT
CloudpressCloudpress
Know what went live
SPIRITT reads your Cloudpress exports, connections and collections to show what went live where, catch docs edited after export, and keep your Docs-and-Notion-to-CMS pipeline healthy.
What you can do with Cloudpress.
A ledger of every export
Each Google Docs or Notion export tracked with its destination and timing.
Pipeline audited end to end
Connections, collections and webhooks checked against the CMSs you publish to.
Stale pages caught
Source docs edited after export are flagged for re-publishing.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your content or editorial operations team.
02
Connect Cloudpress
Add your Cloudpress API key, then connect your Docs, Notion and CMS.
03
Hand over the oversight
Ask SPIRITT to track exports and audit the pipeline. It reports and follows up.
Hand over a mission.
Choose a mission. Make it yours.
Put Cloudpress to work.
See your whole publishing pipeline
Questions
Cloudpress, with SPIRITT.
01What can SPIRITT see in Cloudpress?+
Document export history, connections, collections, webhooks and your account details.
02How does it find stale content?+
It compares each export's time with the source doc's latest edit in Google Docs or Notion and flags anything changed since.
03Can it filter connections?+
Yes. Connections can be filtered by kind, type and source reference.
04Does it start exports?+
Exports run in Cloudpress. SPIRITT tracks them, audits the pipeline and drives the follow-up with your team.
05What can it build around Cloudpress?+
Publishing ledgers, dashboards, client reports and editorial alerts tied to your docs and CMS.
06What does the connection need?+
A Cloudpress API key.