Skip to main content
A few practices that prevent the most common Make-side problems with Magic Meal Kits modules.

​
Finding the modules

  • Notion Plus is a Pro feature — it requires a Pro license. If a module is missing in Make, also make sure the Notion Plus app is added and its connection is set up.
  • Set up and manage all connections at make.magicmealkits.com/connections.

​
Timeouts and retries

When a Notion write fails, the Magic Meal Kits server retries internally before giving up. If those retries run long, the Make module can hit its time limit and surface a timeout.
Set an explicit timeout on long-running requests (a few seconds is typical), and keep each call within limits — for bulk operations, stay at ≤100 records per call.

​
Avoid duplicate runs

Make’s “allow storing of incomplete executions” option re-runs failed scenarios. Combined with the server-side retry above, this can look like duplicate writes. If you see repeats, review that setting on the scenario and decide whether re-running on failure is what you want.

​
Stay within Notion rate limits

The Notion Plus modules are rate limited to about 3 requests/second (matching Notion’s own API). Don’t fan out parallel branches that blow past this — throttle or batch instead. See the Notion API overview for bulk limits and the optional config block.

​
Markdown content

Notion Rich Text blocks have a 2,000-character limit per block, so Magic Meal Kits splits long markdown into multiple blocks when converting. Raw and Refined outputs can differ slightly in length/wording — pick the one that matches your use case. Details in the Notion API overview.