Data Enrichment
Data enrichment in Adeptia lets you look up and attach additional information to records during an integration, drawing from external databases, APIs, CSV files, and code translation tables maintained inside the platform.
What data enrichment does
When a record moves through an integration, it often carries only a subset of the information a downstream system needs. Data enrichment fills that gap by querying a registered data source at runtime and merging the result into the record before it is delivered. For example, a transaction that arrives with only a customer identifier can be enriched with the customer's name, address, and account status before it reaches the target system.
Enrichment is designed to be reusable: you register a source once and reference it across as many integrations as you need.
Enrichment source types
You can register four kinds of enrichment sources. Each is given a unique name and stored persistently, scoped to your tenant.
| Source type | What it connects to |
|---|---|
| Database | A relational database (PostgreSQL, MySQL, or SQL Server) |
| API | An external HTTP service that returns JSON |
| CSV | A hosted CSV file, cached for performance |
| Value map | A code translation table managed inside the platform |
Database credentials are never stored as literal values; you supply a reference to a securely stored credential instead.
Code translation tables: value maps and multi-valued maps
The platform provides two kinds of built-in translation tables that you can create, inspect, update, and delete without leaving the platform.
Value maps are simple crosswalk tables: each source code maps to exactly one target code. They are useful for translating status codes, currency codes, country codes, and similar enumerations. Value maps can be scoped globally or to a specific project.
Multi-valued maps extend this concept by allowing a single source key to resolve to several output values simultaneously. For example, a country code could map to a country name, a region, and a currency code all at once. Like value maps, multi-valued maps can be scoped globally or to a specific project, and global and project namespaces are kept separate.
Value maps can be imported from your Adeptia Automate instance, making it straightforward to reuse crosswalks that already exist in your environment. The import process uses content comparison to skip tables that have not changed, so re-importing is safe to run repeatedly.
How lookups work
When an integration runs, the enrichment capability queries the registered source using a field from the incoming record as the lookup key and returns the matching fields from the source. You choose which fields to return; if you do not specify, all available fields are returned.
You can also chain multiple lookups together in sequence. In a chained lookup, the result of one source query becomes the input key for the next, allowing you to traverse bridge tables or join across sources that do not share a direct key. Chains can span up to five steps.
Filters can be applied at each step to narrow results, supporting equality, inequality, and set-membership conditions.
Managing translation tables
You can perform the full range of create, read, update, and delete operations on both value maps and multi-valued maps directly through the platform. This includes:
- Creating a new table with a name, scope, and set of entries or columns
- Updating or renaming an existing table
- Inspecting a table's current contents before referencing it in a mapping
- Removing a table that is no longer needed
Deleting a translation table is permanent. If a deployed mapping references a table that has been removed, that mapping may fail at runtime.
Scope and access
Both value maps and multi-valued maps can be created at global scope, making them available across the entire instance, or at project scope, limiting them to a specific project. Global and project namespaces are kept separate, so a map created at project scope must be accessed with its project context. When listing available maps, the scope and project association are shown so you can identify the correct map to reference.
For value maps specifically, only project-scoped maps expose their full entry contents for inspection. A value map at Global or Group scope that exists in the platform will appear in the list but its individual entries cannot be retrieved directly; to inspect its contents, recreate it at project scope.