Coda + Data Alias: Save a protected copy as a new Coda page, with a token that stays in your tab
Why use Coda with Data Alias
Reports and tables end up in Coda docs where the rest of the team reads them. This puts the protected copy there directly, so nobody has to download a file, remember which copy was the safe one, and upload it again.
How it works
Coda uses API tokens instead of a sign-in. You paste a token; Data Alias keeps it in this tab's memory only and sends it in an Authorization header to Coda, never to a Data Alias server. You pick a doc and a page name, see exactly what will be sent, and Data Alias creates a new page. It never edits or deletes a page — the only request it can make to a doc is a page creation.
What it does
- Create a new page in a doc you pick, from the protected copy
- Refuse a page name that doc already uses, rather than adding a second page
- Check for that page by name when an answer is lost, instead of sending again
- Show the token only as a mask, and forget it on request, on sign-out and when the tab closes
How it will connect
These are the steps once the connection is available. Until then: Download the safe copy and paste or import it into a Coda page yourself — the same content, moved by hand.
- 1
Create an API token in Coda
Account settings → API tokens. Restrict it to the doc or workspace you intend to use if you can.
- 2
Read where the token will be kept, then paste it
Data Alias shows those terms above the field, before you paste.
- 3
Pick a doc and name the page
You see a preview of the protected copy and the page name before anything is sent.
- 4
Save
A new page appears in that doc. If Coda's answer is lost, Data Alias looks the page name up rather than creating a second one.
What moves where
- What reaches Data Alias servers
- Nothing. There is no server step at all — your browser talks to Coda.
- Where the token is kept
- This tab's memory. Never in storage, a cookie, a URL or a Data Alias server.
- What Data Alias sends
- The protected copy you reviewed and the page name you typed.
- Never sent
- The original file, the alias mapping, and restored results with real names never leave your browser.
Limits worth knowing
- A Coda token is as wide as your account unless you restrict it when you create it — wider than the four calls Data Alias makes with it: identify you, list your docs, look one page name up, create one page.
- Coda allows two pages with the same name, so Data Alias enforces the rule instead: a name already used in that doc is refused.
- Coda applies a new page a moment after it answers, so the page can take a few seconds to appear, and Data Alias links you to the doc rather than to a page URL it cannot yet know.
- “Forget this token” removes it from Data Alias; it doesn't revoke it. Delete the token in Coda when you're done.
Can I connect Coda today?
No. The connection is built and tested against stand-ins for Coda, but it hasn't been run against a real Coda account, so there is nothing to connect yet. Download the safe copy and paste or import it into a Coda page yourself — the same content, moved by hand.
Can Data Alias change a page I already have?
No. The only request it can make to a doc is creating a page. There is no code for editing or deleting one, and the tests check that against the source.
What happens if the save is interrupted?
The save is marked as needing a check rather than as done, and nothing is resent on its own. Checking looks for a page with that exact name in that doc: if the first attempt landed, that page is reported as saved instead of a second one being created.
Where is my API token kept?
Only in this tab's memory. It isn't written to local storage, session storage, IndexedDB or a cookie, and a refresh clears it.
Data Alias reduces exposure risk but cannot guarantee detection of every sensitive value. Every transfer passes the same review as a download — check the result before you send it. How connected services are handled.