Issues with Notion Shorthand modules (v2) when configuring with blueprint

Questions
,
1

:bullseye: What is your goal?

Convert Notion longhand modules for “Create” and “Update” modules to shorthand modules, to cut down on module load time, using blueprint export/re-import.

:thinking: What is the problem & what have you tried?

I’m writing to report several issues I’ve encountered while converting Notion longhand (v1) modules to shorthand (v2) across 50+ scenarios via BLUEPRINT (export/re-import). These are reproducible and affect the reliability of the new modules.

I’ve listed them in priority order:

  1. FILES & MEDIA PROPERTY TYPE MISSING (Critical)
    The shorthand module has no “files” value type available in the field type dropdown. When a Notion database has a Files & Media property, the field appears in the module but there is no valid type to select. Selecting “URL” does not work because Notion’s API expects files as an array of objects with type/external/url structure, not a plain URL string. This means there is currently no native way to write to a Files & Media property using the shorthand module. My workaround is a separate “Make an API Call” module for every files field, which defeats the purpose of the streamlined shorthand module.

  2. MAP TOGGLE STATE INCORRECT AFTER CONVERSION (High)
    After conversion, the Map toggle on fields ends up in the wrong state — in both directions. Some fields that should have Map ON are set to OFF, and some that should have Map OFF are set to ON. This causes “item.value.map is not a function” errors.

The correct behavior should be:

  • Relation field + mapped pill from a previous module → Toggle ON
  • Relation field + hardcoded UUID string → Toggle OFF
  • Any non-relation field (text, number, select, etc.) + mapped pill → Toggle OFF

In short: Map toggle should only ever be ON when the value type is relation AND the value is a mapped pill. In all other cases — including non-relation fields that contain mapped pills — the toggle should be OFF.

What makes this especially painful is that the Map toggle state is UI-only metadata — it does not exist anywhere in the blueprint JSON. This means there is no way to fix it programmatically via blueprint editing. Unlike Issue 3 below, which I can fix in bulk with a script before import, this one requires manually opening every affected module in the UI and checking each field’s toggle one by one. Across 50+ scenarios, that’s not scalable.

Ideal fix: The module should auto-detect the value type and source, and set the toggle state accordingly.

  1. RELATION FIELDS LOSE ARRAY WRAPPING
    During conversion, some relation values lose their array wrapper. A value that should be [“{{expression}}”] becomes just “{{expression}}” as a bare string. The shorthand module requires these to be wrapped in an array.

Issues 3 is fixable via blueprint JSON editing before import, and I’ve built a script to handle them in bulk, but it is still not intuitive for this to happen. Issues 1 and 2 require changes on Make’s side.