Skip to content
  1. Extras
  2. amoConnector
  3. Field mapping

Field mapping

The component uses a flexible field mapping system to send order and form data to amoCRM.

Manager

Mapping is configured in CMP: AppsamoConnectorField mapping tab.

Each mapping row has:

FieldDescription
Contextorder (ms2 orders) or form (forms)
Source fieldField name in MODX (e.g. receiver, email, cost)
Target entitylead or contact
Target fieldStandard amoCRM field (name, email, phone, price) or custom field ID
ActiveEnable/disable this mapping

Default mappings

On install, default mappings are created:

Orders → Contact

Source fieldamoCRM field
receivername
emailemail
phonephone

Orders → Lead

Source fieldamoCRM field
costprice (budget)

Forms → Contact

Source fieldamoCRM field
namename
emailemail
phonephone

Available order fields

Inactive mappings for all available order fields are also created:

  • msOrder: num, cart_cost, delivery_cost, weight
  • Related: status_name, delivery_name, payment_name
  • msOrderAddress: country, index, region, city, metro, street, building, entrance, floor, room, comment, text_address
  • Synthetic: _products_text, _products_count

To use them, open CMP, enable the needed fields and set target amoCRM fields.

Custom amoCRM fields

To map to custom amoCRM fields, put the numeric field ID in Target field. Custom field IDs can be found in CMP (when loading from API) or in amoCRM.