The Get Date command (or its equivalent) in any coding system, automation platform, or scripting environment always expects the date in a specific, structured format — not as plain text, rich text, or random phrases. Dates are a data type, not just a string of characters.
If you input a date as rich text, casual text, or improperly formatted text, it will not automatically be understood as a "date" by the system. To work correctly, the text must first be parsed and converted into a valid date object using a platform-specific function or parsing tool — for example, functions like DATEVALUE(), STR_TO_DATE(), or even "Parse Date" actions in tools like Shortcuts.
This rule is universal:
- In Excel or Numbers, typing "April 26, 2025" will try to be understood, but if you style it weirdly or format it as rich text with embedded fonts, colors, or links, Excel won't know what to do until you clean and convert it.
- In iPhone Shortcuts, using "Get Date" expects a true Date object, not a fancy formatted note or a decorated rich text field. If you paste in styled text, the shortcut will either fail or treat it as plain text — and then you need to use a "Date" action to properly parse and convert it into an actual Date.
- In databases, JSON, and programming languages (like Python, Swift, JavaScript), same deal — if you feed in a random "looking-like-a-date" string, the code will squint suspiciously at it and often throw errors or give wrong results unless explicitly converted.
Bottom Line:
Anytime you're working with dates in any tech system, remember:
"If it looks like a duck and quacks like a duck, it's still not a date until you make it one properly."