Skip to main content
The most common questions from the community, with the fix for each. For server-level operations (503 errors, slow server, logs, stopping the service) see the Troubleshooting guides.
Two things to check:
  • Notion Plus is a Pro feature. It requires a Pro license — make sure your deployment uses a Pro license.
  • Add the Notion Plus app and set up its connection. The modules appear in Make once the Notion Plus custom app is added and connected. Manage connections at make.magicmealkits.com/connections.
Bulk Notion (벌크노션) is a separate product. It automates Notion template updates directly and does not require a Magic Meal Kits install or a Make connection — so its features won’t appear as Make modules.
The most common cause is that your Notion integration hasn’t been granted access to the page or database you’re automating. Issuing the token is not enough — you must add the integration to the page/DB itself.Full step-by-step fix: Fix Notion connection & permission errors.
Two separate effects to know about:
  • Timeouts. When a Notion write fails, the Magic Meal Kits server retries internally. Those retries can exceed the Make module’s time limit and surface as a timeout. Set an explicit request timeout and keep payloads within limits.
  • Duplicate runs. Make’s “allow storing of incomplete executions” option re-runs failed scenarios, which can look like duplicate writes. Review that setting if you see repeats.
More detail: Make integration tips & gotchas.
Connection setup and management is centralized at make.magicmealkits.com/connections. Your deployment’s API URL and key are shown there (and on the App Status page) — you don’t configure them by hand. See Authentication.
These are covered by the Troubleshooting guides:

Persistent 503 errors

Slow / out of memory

Share system logs

Stop or reinstall