Notion Connector
6 min read
Connect your Notion workspace to build custom portals, roadmaps, changelogs, and dashboards powered by your pages and databases.
Who can do this: Owners, Admins, and Editors can add and manage project connectors. See Roles and Permissions for details.
Connect your Notion workspace once and build anything from your existing content. Roadmaps, client portals, changelogs, knowledge bases, all powered by your pages and databases.
What you can do
Access your workspace data:
- Read pages, databases, and nested content
- Browse database properties and views
- Access blocks, text, and embedded media
- Query filtered and sorted database entries
Build custom tools:
- Visual product roadmaps with timeline views
- Client portals showing project status and milestones
- Public changelogs from release databases
- Knowledge bases with custom navigation and search
Keep Notion as your source of truth:
- Updates in Notion reflect in your app
- No copy-paste or manual syncing
- Your team keeps working in Notion
- External audiences get a polished interface
Two ways to connect
Notion works with Sticklight at two levels, depending on what you’re building.
Connector (for building)
The Notion connector lets Sticklight access your workspace while you build. Connect once and Sticklight can read your databases, pull page content, and show you live data in the editor.
Use this for: Roadmaps, portals, dashboards, anything that displays your Notion data.
API key (for live app updates)
When you build something that needs to stay in sync with Notion after publishing, like a changelog that updates when you add releases, Sticklight needs your Notion API key. This lets your published app fetch fresh data from Notion.
Use this for: Public changelogs, live dashboards, anything where your app should reflect Notion changes in real time.
Sticklight prompts you for the API key when it’s needed. You don’t have to set it up in advance.
Available data
Once connected, your project can access:
| Data | What you get |
|---|---|
| Databases | Properties, rows, filters, sorts, views |
| Pages | Title, content blocks, nested pages |
| Blocks | Text, headings, lists, toggles, callouts, embeds |
| Properties | Text, numbers, dates, selects, multi-selects, relations, formulas |
| Content | Rich text formatting, inline mentions, links |
Common use cases
Visual product roadmap
A timeline view of your Notion projects database. Items spread across quarters with color-coded status, filterable by team or priority. Stakeholders see the plan without needing Notion access.
“Build a roadmap from my Notion Projects database. Show items on a horizontal timeline using Start and End dates. Color-code by Status and let users filter by Team.”
Connection needed: Connector only
Client portal
A branded portal where each client sees their project status, tasks, milestones, and documents. Data comes from Notion, but clients get a clean interface without needing Notion accounts.
“Create a client portal from my Notion workspace. Show each client their active tasks, project milestones, and shared documents with a progress overview.”
Connection needed: Connector + API key
Public changelog
Your release history as a polished public page. Version badges, dates, and feature lists pulled from your Notion releases database. Add a release in Notion and it appears on your changelog.
“Build a public changelog from my Notion Releases database. Show version number, date, and features as formatted cards with newest first.”
Connection needed: Connector + API key
Knowledge base
Your internal docs transformed into a public-facing help center. Navigation, search, and categories built from your Notion page structure. Keep writing in Notion, publish everywhere.
“Turn my Notion Docs workspace into a searchable knowledge base with categories, article pages, and a search bar.”
Connection needed: Connector + API key
Connecting Notion
Step 1: Connect the connector
You can connect from chat or from your project settings.
From chat:
“Connect my Notion workspace”
From project settings: Open Settings, go to Connectors, and select Notion.
When you start the connection:
- Click Connect Account.
- Log in to Notion when the authorization window opens.
- Select the pages and databases you want Sticklight to access.
- Click Allow to authorize Sticklight.
Once connected, Sticklight can access your selected Notion content while you build.
Step 2: Add your API key (when needed)
If you’re building something that needs live updates after publishing, Sticklight enables Cloud Backend automatically. This provides the backend function needed to securely fetch data from Notion. Then it prompts you for your Notion API key.
To create an API key:
- Go to notion.so/my-integrations
- Click New integration
- Name it (e.g., “Sticklight App”)
- Select your workspace and click Submit
- Copy the Internal Integration Token
- Paste it into Sticklight when prompted
- In Notion, share the relevant pages/databases with your integration
The key is stored securely and only used by your published app to fetch data from Notion.
Sharing pages with your integration
Notion integrations can only access pages you explicitly share with them. After creating your API key:
- Open the Notion page or database you want to use
- Click Share in the top right
- Click Invite
- Search for your integration name and select it
- Click Invite
Repeat for each page or database your app needs. Child pages inherit access from their parent.
What visitors see
When you publish your app, anyone with the URL can view it. This includes any Notion content you choose to display.
Before publishing, consider what information you’re sharing. A client portal meant for specific clients shows different data than a public changelog. You control what your app displays, so build with your audience in mind.
Limitations
- Workspace-level access. The connector accesses one Notion workspace per connection. For multiple workspaces, create separate projects.
- Explicit sharing required. Your integration only sees pages you share with it. Share parent pages to include all child content.
- API rate limits. Notion limits API requests. High-frequency updates may be throttled.
- Read-focused. Most Notion apps are read-only displays of your content. Writing back to Notion requires additional setup.
FAQ
Does connecting Notion cost anything?
No. Connecting is free. You only spend credits when you build something.
Will this change anything in my Notion workspace?
No. Your pages, databases, and content stay exactly where they are. Apps you build read that data and display it in a new format. Notion remains your source of truth.
What’s the difference between the connector and the API key?
The connector lets Sticklight read your Notion data while you build. The API key lets your published app fetch fresh data from Notion. Static displays only need the connector. Live-updating apps need both.
Why do I need to share pages with my integration?
Notion integrations have no access by default. Sharing pages tells Notion which content your app is allowed to read. This keeps your private workspace content private.
Do I need to know how to code?
No. Describe what you want in plain language and Sticklight builds it. If you do write code, the files are there to open and edit.
How do I get the best results?
Name the specific database and describe which properties to use. Instead of “build a roadmap,” try “build a roadmap from my Projects database using Status for color, Team for filtering, and Start/End dates for the timeline.”
Can I share what I build with clients?
Yes. Publish to your project URL and send the link. Your app, your brand, your data.
Can I connect multiple Notion workspaces?
Each project connects to one Notion workspace. For multiple workspaces, create separate projects.
Last updated: August 2, 2026