Notion + Data Alias: Save a reviewed, protected result as a new Notion page
Why use Notion with Data Alias
Once the analysis is done, the result usually belongs on a team page. This saves it there after review, with aliases still in place, so real names never land in your workspace.
How it works
Notion's API can't be called from a browser, and signing in needs a secret, so Notion saves go through a Data Alias relay. You connect with the Insert content capability only: Data Alias can add pages where you allow it but cannot read your workspace. Because it can't list your pages, you paste the link of a page you shared during sign-in, or save to a private page. The protected result passes through the relay to Notion and is neither stored nor logged by our code.
What it does
- Save a protected table as a new page, up to 1,000 rows and 30 columns
- Save an aliased AI answer as a new page, up to 200,000 characters
- Create a private workspace page, or a new page inside one you shared
- Revoke both tokens with Notion when you disconnect
How it will connect
These are the steps once the connection is available. Until then: Download the safe copy from Data Alias and add it to a Notion page yourself.
- 1
Connect with Insert content only
Notion's consent screen asks for Insert content and no user information. During sign-in, share the page you want results saved under.
- 2
Choose what to save
Pick the protected copy, or paste an AI answer that still carries aliases.
- 3
Paste a page link and a title
Data Alias can't browse your workspace, so paste the link of a page you shared, or choose a private workspace page.
- 4
Save as a new page
The page is created and its link is shown. Nothing existing is edited.
What moves where
- What reaches Data Alias servers
- The protected result and its title, in transit to Notion. Not stored and not logged by our code.
- What Data Alias reads from Notion
- Nothing. Insert content does not allow reading pages.
- Never sent
- The original file, the alias mapping, and restored results with real names never leave your browser.
- Who holds the access token
- Our server, sealed in an encrypted cookie that page scripts cannot read.
- When you disconnect
- Both tokens are revoked with Notion and the cookie is deleted. Pages you saved stay in Notion.
Limits worth knowing
- If the answer to a page create is lost, Data Alias has no read access to check, so it asks you to look in Notion first. Creating it again may make a second page.
- Creating a page inside a shared page adds it to that page's list of children, which is a visible change to that page.
Can I connect Notion today?
No. The connection is built and tested against stand-ins for Notion, but it hasn't been run against a real Notion account, so there is nothing to connect yet. Download the safe copy from Data Alias and add it to a Notion page yourself.
Can Data Alias read my Notion workspace?
No. It connects with Insert content only, and there is no search, read or update call in the code.
Why does Notion go through your server when Google doesn't?
Notion's API doesn't accept calls from a browser, and signing in needs a secret that can't live in a web page. The relay passes the protected result on to Notion without storing or logging it.
Can it add to an existing page?
Only to a page it created itself in the same save. Adding content requires a receipt the relay signed when it created that page, so an arbitrary page can't be appended to.
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.