---
title: "Filename to metadata field mapping integration"
date: "2025-07-30T05:10:21+00:00"
summary: "Automate metadata extraction from filenames in <span class=\"mention\" data-mention=\"#822\" data-plugin=\"product\" data-mention-uuid=\"68219b5b-0b6f-4877-8625-78eea778a0c5\" data-entity-type=\"taxonomy_term\" data-entity-uuid=\"9cbd8789-1274-426f-ad7c-8dfbbb2dc8e1\">Acquia DAM (Widen)</span></span></span></span>. Map components to fields for efficient, accurate asset tagging."
image:
type: "page"
url: "/acquia-dam/filename-metadata-field-mapping-integration"
id: "0143437d-de46-4416-9ffd-efe1f64c821c"
---

What is filename mapping?
-------------------------

The filename mapping native integration provides an automated workflow that extracts metadata from filenames and populates the corresponding fields in Acquia DAM (Widen) to create a more efficient, accurate metadata tagging process. This integration detects new file uploads, parses filenames using specified delimiters, and maps the components to designated metadata fields.

How it works
------------

When a new file is uploaded to DAM, the integration:

*   Detects the new file upload.
*   Parses the filename using predefined delimiters.
*   Maps each filename component to specified metadata fields.
*   Populates the metadata in assets automatically.

**Key features**

*   Automated metadata extraction from filenames
*   Real-time detection of new uploads
*   Customizable filename parsing with delimiters
*   Support for lookup table value mapping
*   Filter options by upload profile, metadata type, asset group, global collection, or assets search query

**Limitations**

*   Maximum of 20 metadata field mappings permitted
*   Triggers only on new file uploads, not on renamed files
*   Requires exact matches for controlled metadata values
*   Integration does not modify metadata types, asset groups, or global collections
*   No user interface components, operation is background only

Setting up the integration
--------------------------

**Required documentation**

*   [Filename mapping worksheet:](https://docs.google.com/spreadsheets/d/15lOGEU489tPY88-1u3w-SwZijW1Yl_a8mlefQpmYm3Y/copy)
    *   Define mappings between filename components and metadata fields.
    *   Create separate tabs for different filename conventions.
    *   Include an identifier for each convention type.
*   [Lookup table worksheet:](https://docs.google.com/spreadsheets/d/1ZFxjak-0zySKFOPpRpFTOmaTTmn47B9Cj7kP3RpdWhI/copy)
    *   Specify filename component codes or keys.
    *   Define corresponding DAM values.
    *   Use exact matching criteria.
*   Filter configuration:
    *   Determine trigger criteria.
    *   Specify applicable asset groups or profiles.

**Important considerations**

*   Controlled vocabulary fields require exact matches.
*   Lookup table values must be precise for the integration to function.
*   Avoid using multiple automations on a single field.
*   Field permissions affect integration functionality.

**Best practices**

*   Use position-based mapping in lookup tables.
*   Follow consistent filename conventions.
*   Validate mapped values regularly.
*   Monitor integration performance.

**Support and maintenance**

*   The Support team monitors integration performance.
*   The system provides error notifications.
*   Submit changes or requests through support cases.
*   Review configuration regularly.

For notifications about new uploads, use the DAM Paths feature separately from this integration.