Notion Select Fields Require Cryptic IDs Instead of Values - Is This Expected Behavior?

Questions
1

Hi n8n community! :waving_hand:

I’m working with the Notion node and running into what seems like a UX issue with Select fields. I wanted to check if this is expected behavior or if I’m missing something.

The Problem

When setting values for Notion Select properties through an expression (and not fixed), the node requires internal option IDs instead of the actual readable values. For example:

  • Instead of using "completed" → I need to use "1a2c096b-ffd0-407a-a395-65a49d5bb92b"
  • Instead of using "refunded" → I need to use "=cZC"
  • Instead of using "EUR" → I need to use "<rpF"

Why This Is Problematic

  1. Poor maintainability: If I add new options in Notion, I need to hunt down cryptic IDs
  2. Error-prone: These IDs are impossible to remember and easy to mistype
  3. Inconsistent UX: Other automation tools (like Zapier) accept the actual values directly
  4. Debugging nightmare: When something breaks, seeing "=cZC" in logs tells me nothing

Current Workarounds

I’ve found these alternatives:

  • Create a mapping object to translate values to IDs
  • Use rich_text fields instead (but loses Select functionality)

Questions

  1. Is this the intended behavior for the Notion node?
  2. Is there a hidden “Use Names” option I’m missing?
  3. Are there plans to improve this in future versions?
  4. What’s the recommended approach for handling Select fields?

I love n8n’s flexibility, but this particular aspect feels like it could be more user-friendly. Any insights from the community would be greatly appreciated!

Thanks! :folded_hands:

2

did you fix it?

3

grafik
grafik1805×725 69.9 KB

It works like this :slight_smile: