Connect the real source
Use supported Sheets and API connections without copying credentials into project chat.
Solution
Keep the graphic current without exposing the source.
Connect Google Sheets or an 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. Credentials stay in a secure connection flow, the server validates supported data, and the viewer reads a published snapshot rather than calling a supplier, spreadsheet or private API directly.
What it helps you do
From source to published story.
Control every refresh
Validate shape, types and publishing rules before a snapshot reaches readers.
Keep the embed stable
Refresh published data without asking the publisher to replace the Smart Embed.
Recover safely
Retain immutable versions and roll back after a bad or incomplete supplier update.
What you can create
Built around the story, not the chart type.
Questions
What teams need to know.
Can I start with a question instead of a dataset?
Yes. Storycards can begin with sourced research or accept data you already have.
Does the published viewer receive source credentials?
No. Connected sources are handled server-side and public delivery receives a sanitized package.
Can the visual still be edited after the first draft?
Yes. Data, copy, layout, chart styling, interaction and motion remain structured and editable.