Skip to main content
By far the most common Notion issue is a permission error: the integration token is valid, but it hasn’t been granted access to the specific page or database you’re automating. Issuing the token is only half the setup.

​
When you need this

Symptom: Notion modules fail with 401, a permission error, or “the connection page has no permission” — even though the token looks correct.

​
Fix

1

Create a Notion integration token

In Notion, create an internal integration and copy its token. This is the value you put in the Notion Token field of the Make connection.
2

Grant the integration access to the page or database

Open the page or database you want to automate, and add your integration to it via its Connections menu (top-right ••• → Connections → add your integration). Add it at the top-level page/DB so child pages inherit access.
This is the step most people miss. A token with no access to the target page returns 401 / permission errors on every call.
3

Register the connection in Make

Enter the Notion Token (and, for unofficial operations, the Space ID and User ID) on the Make Notion Plus connection. Manage your connections at make.magicmealkits.com/connections.
4

Test with a simple value first

Run the module with a plain text input to confirm the connection works, then build up to your real payload. This isolates a permission problem from a data/formatting problem.

​
Still failing? Re-set the connection

If access is granted but calls still fail, the stored session may be stale. Re-register the Notion connection — log out of Notion, then reconnect while logging back in. Re-creating the connection clears most cookie/session errors.
For other Magic Meal Kits products (Plaud, Tiro, Threads) the per-service credentials are stored server-side — reconnect those accounts from make.magicmealkits.com/connections. Notion is the exception: the token is supplied per request. See Authentication and the Notion API overview.