Connect Notion

FyneDesk's Notion connection lets your team send ticket context to Notion, sync knowledge base articles with Notion pages, and let AI use selected Notion content when drafting replies, summaries, and triage suggestions.

Admin setup, Pro plan Notion is an organization-level connection. A FyneDesk admin connects it once from Settings → Connections → Notion, and the workspace must be on Pro to use it.

What the connection does

Ticket → Notion: create a linked Notion page in a selected database when a ticket is created, escalated, or tagged.
Knowledge base sync: publish FyneDesk-owned KB articles into Notion, or import selected Notion pages as Notion-owned KB articles.
AI knowledge source: let FyneDesk AI use selected Notion pages and databases alongside your KB and past tickets. If you map statuses, changes in Notion can also update the linked FyneDesk ticket status.

Before you start

You must be a FyneDesk organization admin.
Your FyneDesk workspace must be on the Pro plan.
You need access to the Notion workspace, pages, and databases you want FyneDesk to use.
You do not need to create a Notion developer app or configure Notion webhooks. FyneDesk handles the connection after you authorize it in Notion.

You choose what FyneDesk can see During Notion authorization, pick the exact pages and databases to share. FyneDesk can only access those selected items and their children. If a page, database, or article does not appear later, first check whether it was shared with FyneDesk in Notion.

Step 1 — Connect Notion

In FyneDesk, open Settings → Connections → Notion.
Click Connect.
Notion opens an authorization screen. Choose the correct workspace.
In the Notion page picker, select the pages and databases FyneDesk should be allowed to use.
Return to FyneDesk. The Notion connection page should show the connection status and setup options.

Step 2 — Turn on the connection

The master enable toggle starts off. After Notion is connected, turn the connection on from the Notion settings page. Keep it off if you want to finish choosing databases, sync rules, and AI sources before anything starts moving.

Step 3 — Configure Ticket → Notion

Use Ticket → Notion when a ticket should become planned work in Notion, such as an engineering escalation, product bug, feature request, documentation gap, or operations follow-up.

Choose the target database in Notion. This is the database where FyneDesk creates the linked page.
Choose the trigger: on create, on escalate, or on tag.
Optionally map FyneDesk fields to Notion properties so the Notion page lands with the right status, owner, priority, or category fields for your workflow.

When the trigger runs, FyneDesk creates a Notion page with the ticket title, key fields, and a link back to the ticket. FyneDesk does not create duplicate Notion pages for the same ticket.

Step 4 — Configure KB ↔ Notion sync

Knowledge base sync has two directions. You can use either one or both, depending on where each article should be edited.

Publish target: choose the Notion location where FyneDesk-owned knowledge base articles should be published.
Import sources: choose Notion pages or databases that should be pulled into FyneDesk as Notion-owned KB articles.
Default owner: choose whether newly linked articles should be owned by Notion or by FyneDesk.

How article ownership works

Each synced article has one owner, also called the source of truth. If FyneDesk owns the article, edit it in FyneDesk and Notion shows a read-only mirror. If Notion owns the article, edit it in Notion and FyneDesk shows a read-only mirror.

The mirror side may show an “edited in Notion” or “edited in FyneDesk” badge so your team knows where changes belong. FyneDesk does not merge competing edits between both sides. To change where an article should be edited, switch the owner for that article.

Sync timing FyneDesk-owned article changes publish to Notion shortly after publish or edit. Notion-owned changes are usually picked up shortly after the Notion edit, often around a minute, but can take a few minutes. FyneDesk also uses a periodic backstop in case a Notion event is delayed.

Step 5 — Let AI use Notion

To make Notion content available to FyneDesk AI, choose the Notion pages or databases under AI sources and turn on the AI source toggle. This toggle starts off by default.

When enabled, AI reply drafts, summaries, and triage suggestions can draw from selected Notion content alongside your FyneDesk knowledge base and past tickets. Editing a selected Notion page refreshes the AI knowledge source after sync and indexing run.

Step 6 — Map Notion statuses back to tickets

If your Notion tracker uses statuses, you can map Notion status values to FyneDesk ticket statuses or actions. After mapping, changing the status on the linked Notion page can update the linked ticket in FyneDesk.

Status sync is loop-safe: a status update should not bounce endlessly between FyneDesk and Notion.

Monitor connection health

The Notion connection page shows health details such as the last sync or event time and subscription status. Check this area when a ticket, article, or AI source does not seem current.

Limits to know

FyneDesk only sees the pages and databases selected in Notion's authorization picker.
Knowledge base sync is not a perfect Notion layout clone. Plain text, headings, lists, tables, images, code blocks, quotes, toggles, and callouts convert cleanly. Embeds, link previews, and complex layouts may be simplified or replaced with placeholders.
Very large Notion pages, around 20,000 blocks or more, may be truncated.
Sync is not instant. Allow a minute or a few minutes for changes to appear.
Each synced KB article has a single owner. The mirror side is read-only until you switch ownership.
The Notion connection requires the Pro plan.

Troubleshooting

FyneDesk says to reconnect Notion. The Notion authorization may have expired or been revoked. Open Settings → Connections → Notion and connect again. Sync resumes after the connection is restored.

A ticket or article is not syncing. Confirm the master toggle is on, the relevant feature toggle is on, and the Notion page or database was shared with FyneDesk during authorization. For KB articles, also check which side owns the article.

AI is not using Notion content. Confirm the AI source toggle is on, the page or database is selected as an AI source, and enough time has passed for sync and indexing.

I cannot find a Notion page or database in FyneDesk. Reconnect Notion and make sure that item is selected in the Notion page picker. FyneDesk cannot list pages or databases it was not allowed to access.

Manage or disconnect

To change shared pages, refresh permissions, or recover from revoked access, reconnect Notion from the same page. To stop the integration, click Disconnect. Disconnecting removes stored Notion tokens and configuration from FyneDesk and pauses Notion sync until an admin connects again.

Privacy & access

Notion access is scoped to the pages and databases selected by your admin in Notion. FyneDesk does not receive access to your entire Notion workspace unless those pages are explicitly shared. The connection is organization-level, so admins should select only the pages and databases needed for ticket handoff, KB sync, and AI knowledge.

Need a hand? Email support@fynedesk.io and we will help you get connected. For an overview of the integration, see the Notion integration page.