DynamoDB numeric strings can now stay as strings
The AWS DynamoDB node in n8n now includes a toggle letting users prevent numeric-looking strings from automatically converting to Number type, solving a long-standing pain point for data integrity.
The AWS DynamoDB node has been auto-converting numeric-looking strings — values like "34" or "42.5" — into DynamoDB Number type (N) since its creation. This silent conversion could cause unexpected behavior for workflows that needed precise type control.
A new "Automatically Parse Numbers" toggle (enabled by default) gives users the choice. When disabled, only actual JavaScript numbers are stored as N; strings remain as String type (S) regardless of their content. Existing workflows continue working identically since the default preserves the original behavior.
The change applies to PutItem and upsert operations in the n8n AWS DynamoDB integration.
View Original GitHub Description
Summary
Adds an Automatically Parse Numbers toggle (default: true) to the PutItem/upsert operation, addressing the issue where numeric strings (e.g. "34") were always stored as DynamoDB Number (N) type.
- When enabled (default): preserves existing behavior — numeric-looking strings are stored as
N - When disabled: only actual JavaScript numbers are classified as
N— strings stay asSregardless of content
This is a non-breaking change: existing workflows continue to work identically.
Based on the approach proposed by @umut-polat in commit be16a1a845, adapted for the current codebase.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-4576
Review / Merge checklist
- PR title and summary are descriptive. (conventions)
- Docs updated or follow-up ticket created.
- Tests included.
- PR Labeled with
release/backport(if the PR is an urgent fix that needs to be backported)