{ "nodes": [ { "parameters": {}, "type": "n8n-nodes-base.manualTrigger", "typeVersion": 1, "position": [ -1248, -1072 ], "id": "4be1dc93-82cc-4162-8f3e-e074e48c32ae", "name": "When clicking ‘Execute workflow’" }, { "parameters": { "language": "pythonNative", "pythonCode": "import traceback\nfrom datetime import datetime\n\ntry:\n s = "01.01.2000 14:30"\n dt = datetime.strptime(s, "%d.%m.%Y %H:%M")\n iso = dt.isoformat()\nexcept Exception:\n return [{"json": {"data": traceback.format_exc()}}]\n\nreturn [{"json": {"data": None}}]" }, "type": "n8n-nodes-base.code", "typeVersion": 2, "position": [ -1024, -1072 ], "id": "45501b6a-b7e3-4012-a41b-5ac0be7d9959", "name": "Code in Python" } ], "connections": { "When clicking ‘Execute workflow’": { "main": [ [ { "node": "Code in Python", "type": "main", "index": 0 } ] ] } }, "pinData": {}, "meta": { "templateCredsSetupCompleted": true, "instanceId": "ae8cd1c0f8a5664e6d74f12084bf9027051d96efbc027ab983b556b365264096" } }

TL;DR

The issue is likely due to a compatibility problem between the Python version used in the n8n node and the datetime library, causing the 'mappingproxy' object has no attribute 'import' error.

Guidance

• The error suggests that there's an issue with how the datetime library is being imported or used within the n8n workflow, possibly due to changes in Python's import mechanism or the library itself.
• Verify that the Python version used by the n8n node supports the datetime library as expected. Given the Node.js version (24.14.1) and n8n version (2.18.5), ensure compatibility with the Python environment.
• Check the n8n documentation for any specific requirements or recommendations for using Python scripts, especially regarding library imports and versions.
• Consider testing the Python script outside of the n8n environment to isolate if the issue is specific to n8n's execution of Python code.

Notes

The provided information does not specify the Python version being used, which could be crucial for diagnosing the issue, as different Python versions have different import mechanisms and library support.

Recommendation

Apply workaround: Test the Python script in a standalone environment to confirm if the issue is n8n-specific or a general Python compatibility problem. This can help in identifying whether the problem lies in the n8n setup or the Python code itself.