Metadata Auto Mapper Action
The Metadata Auto Mapper Action resolves wildcards contained inside metadata values.
Sometimes metadata fields contain placeholders (wildcards) instead of real values. These may appear as raw strings such as {project.name}, {user.name}, or {time.hour} inside the stream. This node evaluates those placeholders and replaces them with their actual values so the metadata can be used reliably in subsequent workflow steps.
Why This Happens
Unresolved metadata can occur in two common situations:
The wildcard is not yet available at trigger time Example: using {project.group} during a Create Project trigger, where the value does not yet exist when the metadata is initially created.
Metadata “Pre-Resolve” is disabled In this case, the metadata keeps the literal string instead of resolving it automatically.
Without correction, the workflow receives the raw string (e.g., {project.name}) instead of the actual value.
Behavior
Scans all available metadata in the stream
Detects wildcard placeholders
Resolves them to their real values
Updates the metadata accordingly
No parameters are required.
Typical Use Cases
resolving timestamps stored in metadata
preparing metadata for export or third-party integrations
fixing metadata created during early triggers (e.g., project creation)
ensuring metadata values can be used for naming, routing, or API calls
Example
Metadata value before node execution:
After the Metadata Auto Mapper Action:
Practical Tip
Place this node before any node that reads or exports metadata (file naming, API calls, XML generation, etc.). If you skip it, downstream systems may literally receive {project.name} instead of the real value — and those errors are notoriously confusing to debug later.
Last updated