Choose and map the source
Start with Google Sheets, a reviewed connector or a supported API, then select the fields, types and rows the visual needs.
Solution
Create live charts and maps without exposing the source.
Connect Google Sheets or a supported authenticated API, validate updates on the server and publish a responsive embed that reads a viewer-safe snapshot.
✦ASK STORYCARDS
Connect this authenticated results endpoint and refresh the published ranking every five minutes
Finding the dataChecking sourcesBuilding an editable draft
READY TO REFINEStructured chart + sourcesOpen in Studio →
Why Storycards
Live for the audience, private at the source
Storycards separates the authoring connection from public delivery. Choose a reviewed connector or configure a supported endpoint, map the response into typed fields, test a sample and define the refresh policy. Credentials remain in the secure connection flow; the public viewer reads the last validated snapshot rather than calling a supplier, spreadsheet or private API directly.
What it helps you do
From source to published story.
Validate every refresh
Inspect a sample and check shape, types and publishing rules before a new snapshot can reach readers.
Keep the embed stable
Refresh a published chart or map without replacing the Smart Embed in the page.
Protect and recover
Keep credentials server-side, retain the last good snapshot and roll back after a bad supplier update.
What you can create
Built around the story, not the chart type.
Questions
What teams need to know.
Does the reader connect to our spreadsheet or API?
No. The server resolves the private connection and the published viewer reads a sanitized snapshot.
What happens when a refresh is invalid?
Validation prevents an incomplete or malformed response from silently replacing the last good published snapshot.
Can a live map use the same connection model?
Yes. A connected source can update the structured geographic data used by a published chart or map while the embed URL stays stable.
Do we need to replace the embed after an update?
No. Publish reviewed snapshots to the same project and preserve version history and rollback.