Data mapping defines how the fields in your document align with fields in other sources, such as CRMs, spreadsheets, or databases. The setup, depending on the bot used, determines how data is transferred. It can either fill documents with data from the mapped fields or move data from the documents to other systems.
Basic steps
To map fields, drag a field from the tree and drop it onto the corresponding document field on the right. Valid target fields will be highlighted in blue. Once mapped, the field name will appear on the canvas.
To unmap fields, hover the mapped field name and choose Unmap, or click the Unmap icon next to the document field.
Click Edit document to add missing fields to a document or change a field’s type.
Field types
The tree shows fields for your base object and its related records.
One-to-one (1-to-1)
Links one record in a related object to exactly one base record.
Example: Opportunity has one User as the owner.
Base object: Opportunity
Related 1-to-1 object: User (chosen in the OwnerId field on Opportunity)
Tree label: User (OwnerId)
One-to-many (1-to-N)
Links one base record to multiple records in a related/child object.
Example: An Account can have several Opportunities.
Base object: Account
Related 1-to-many object: Opportunity (each Opportunity points to the Account via AccountId)
Tree label: Opportunity (AccountId)
How to read the brackets
Related records appear as Target entity (linkField).
For 1-to-1, the linkField lives on the base record → e.g., User (OwnerId) means “OwnerId on the base record points to one User.”
For 1-to-N, the linkField lives on the related record → e.g., Opportunity (AccountId) means “each Opportunity has AccountId pointing back to the base Account.”
Field icons legend
The table shows how each icon in the field tree maps to a data type or a relationship.
Preview values
Preview values show the actual data from a sample record to help you pick the right fields. These values are for guidance only. When the bot runs, it uses data from the record it processes–-not the previewed ones.
How to use:
Turn Preview values On.
Enter a Record ID for your base object and click Apply.
To get a Record ID open the record in your CRM and copy the ID from the page URL.
What you’ll see:
[value] - a sample value from the preview Record ID that confirms you've selected the correct field path.;
[Empty] - the sample record has no value in this field but you can still map it;
[Not Found] - the Record ID is invalid or inaccessible. Correct the ID to view sample data.
[] - loading; the value is being fetched.
Fields search
Quickly locate the right field in the tree while mapping. Search works by field name; with Preview values on, it can also match by a value from the sample record (e.g., an email, phone, or city).
How to search
Type part of a field name (API/internal) in the search box.
If Preview values is On, you can also type a sample value to find the field that contains it.
How search results appear:
The matches are highlighted, not filtered;
Use Next / Previous to jump between matches;
Search returns matches only for the current object and expanded related records.
-To search inside a related record, expand that branch first.
-As you expand more branches, new matches are added to the count.
How to find the names used in CRM (API/internal names)
To get the exact API/internal name, use one of these quick methods:
Salesforce: API Name (Setup → Object Manager → Object → Fields & Relationships → Field).
Microsoft Dynamics 365 / Dataverse: Schema name / Logical name (Power Apps → Table → Columns → Column).
HubSpot: Internal name (Settings → Objects → Properties → Property).
Pipedrive: Key / Field key (Company settings → Data fields).
Zoho CRM: API Name (Setup → Modules and Fields → Module → Field).
Databases/Sheets: column/field name in the table or header row.