08/Data integration
Works with the systems your process knowledge already lives in.
Documents and run data in. Files and an API back out.
Read from the tools your teams already write in, pull run data from the systems the work happens in, and take processes back out as files or through the API.
Data in
Mapper
Data out
Document sources
Connect Google Docs, Microsoft 365, Confluence and Notion
No migration first. Sapeum ingests the documents, transcripts and workspace content your teams already write in.
- Document, transcript and SOP ingestion
- Google Docs, Microsoft 365, Confluence and Notion
Getting data out
Take a process out as a document, image or spreadsheet
The same model becomes a board slide, a procedure document or a spreadsheet analysis without anyone redrawing it.
- Image, vector, document and spreadsheet exports
- REST API for processes and changes
Run data sources
Pull run data from your warehouse, database or spreadsheets
Live process-run data comes from wherever it already lands: a warehouse, a lake, a database, a spreadsheet, or an inbound webhook from the system doing the work.
- Warehouse, lake, S3, SQL and spreadsheet connectors
- Inbound webhook and Microsoft Graph for live runs
Process data lands where teams already work
No extra tool for anyone to remember to open.
Your systems can read the process directly
Through the API, not a document someone must spot.
Design and running system stay closer together
Map and executing system stay connected.
Related features
All featuresCapture processes
Document a process in one working session, from interviews, workshops or the files you already have.
Processes as data
Process maps you can query, update and reuse, with owners, timing and handoffs held as data.
Common questions
What formats can we export to?
Image and vector (PNG, SVG), document (PDF, DOCX) and spreadsheet (XLSX, CSV), so a map can go straight into an SOP or an analysis.
Is there an API?
Yes. A REST API provides programmatic access to processes and their changes, including reading the current live process mid-execution. An attached automation platform pulls from it rather than Sapeum pushing out. For run data coming the other way, Sapeum accepts an inbound webhook alongside warehouse, lake, S3, SQL and spreadsheet connectors.
Which workspace tools can Sapeum read from?
Google Docs, Microsoft 365 (via Graph, including Entra for identity), Confluence and Notion, alongside direct document, SOP and transcript ingestion.
Do we have to move off our existing tools first?
No. Sapeum reads from the places process knowledge already lives, including Google Docs, Microsoft 365, Confluence, Notion, plus documents, SOPs and transcripts, rather than requiring a migration before it is useful.
How does live run data get into Sapeum?
From wherever it already lands: a data warehouse, a data lake or S3, a SQL database, a spreadsheet export, or an inbound webhook posted by the system doing the work. That run data is what process telemetry analyzes.