Connect Notion
How to connect a Notion database, what a published article looks like once it lands there, and what Notion does not carry over.
4 min de lecture
Paid plans
The Notion card sits under Publishing on the Integrations page and adds each finished article as a page in a Notion database of yours. It goes one way only — QuQi writes into Notion and never reads anything back out of it. Like every publishing destination, it takes your one publishing slot.
COMMENCEZ ICI
You need two things from Notion: an integration token, and the database the pages should go into. Sharing that database with your integration inside Notion is not optional — without it Notion will not open the database and the connection is refused.
Connect it
1
Open Integrations
Make sure you are on the right website, then find Notion under Publishing and press Set up.
2
Create an integration in Notion
Go to notion.so/my-integrations and create an internal integration with content capabilities. Copy the token it gives you.
3
Share the database with it
Open the database in Notion, then ⋯ → Connections, and add the integration you just made.
4
Fill in the two fields
The integration token, and the database. You can paste the database’s full address instead of the bare ID — QuQi picks the ID out of it.
5
Press Connect
QuQi opens the database in Notion before it stores anything. If Notion refuses, you see what went wrong and nothing is saved. The token is kept encrypted.
BON À SAVOIR
There is no second step afterwards. Shopify asks which blog and Webflow asks which collection, but you have already named the Notion database yourself, so the drawer just closes. QuQi does work out one thing on its own: which column of the database holds the page title, so a renamed title column still works.
Checking it worked
1
Look at the Integrations page
Notion shows as connected, with your database’s own title underneath. The connection is proven against Notion before it is saved, so a card showing as connected is a working one. The other publishing cards drop their Set up button for an “in use” note.
2
Publish one article by hand
Open a written article on the calendar and press Publish. QuQi tells you it published to Notion, and the article keeps a link to the page it made.
3
Open the page in Notion
Read it there — headings, lists, quotes, code and pictures — before you let autopilot publish on its own.
What lands in Notion
- One new page per article, in the database you named. Nothing else in the database is touched.
- The article title goes into the database’s title column, whatever you have called it. A very long title is trimmed.
- The article’s cover picture becomes the page cover, as long as it is a web address.
- The body arrives as real Notion content: paragraphs, headings, bulleted and numbered lists with one level of nesting, pictures, quotes, code blocks, dividers, and captions under figures. Bold, italic, inline code and links survive too.
- A long article arrives whole — the body is sent in batches, in order, because Notion only accepts so much at once.
What Notion does not carry over
- A table in the article does not become a Notion table. Each row arrives as one line with the cells separated by
|. - A picture that is not at a full web address is dropped rather than shown broken.
- Code blocks lose their language and read as plain text.
- An extremely long article stops after about six hundred pieces of content.
- Nothing but the title and the cover is written. No tags, categories, slug, description, status or date reach any other column of the database — fill those in yourself in Notion if you need them.
ATTENTION
Every publish makes a new page. QuQi cannot go back and update a page it already created, so publishing the same article twice leaves you with two pages in the database — delete the old one in Notion yourself.
When it is refused
When a publish fails, QuQi passes Notion’s own reason straight through onto the card. A connection that is refused is different: the drawer tells you in QuQi’s own words what went wrong, so do not go looking for that wording in Notion. A failed publish turns the card red, prints the reason on it, and swaps Reconfigure for Reconnect.
WHAT YOU SEEWHAT IT MEANSWHAT TO DO
Notion rejected that token
The token is wrong, or it has been removed in Notion.
Copy it again from notion.so/my-integrations.
Notion could not open that database
Either the ID is wrong, or the database was never shared with your integration.
Check the ID, then add the integration under ⋯ → Connections.
That database has no title property
What you pointed at is not a plain database.
Pick a regular Notion database.
That does not look like a database ID
What you pasted has no ID in it.
Paste the database’s full address and let QuQi pick it out.
Notion rejected the stored token
The token worked once and has since been revoked.
Create a fresh one and reconnect.
Part of the body failed to append
The page was made but not all of the article reached it.
Open the page in Notion and check what is missing before republishing.
Disconnecting
Disconnecting removes the stored token from QuQi and frees your publishing slot. It changes nothing inside Notion: your pages stay where they are, and your integration still has access to the database until you remove it there under ⋯ → Connections.
ATTENTION
Letting an agent publish to Notion on its own needs a plan that includes CMS publishing. During the trial the run stops at that point, saves the article, and tells you publishing unlocks once your subscription is active. Pressing Publish on an article yourself is not blocked.