How to Map a field

Mapping default or existing fields Copy Link

We make sure your data flows seamlessly between apps! For that, Wiresk takes care of retrieving data from your integrated source app and sends it to your destination app, it’s called Field Mapping. 

The Field mapping ensures that your data lands in the right place. 

In most cases, Wiresk will create the mapping for you based on common field names. However, you can personalize your field mapping as you see fit: 

1. Simply click on the field you want to map in your destination app. 

2. Choose your mapping method: 

Flow input Copy Link

click on the input field, here you can select preloaded data from your Trigger or your Previous Method. 

You can Map the “Input “field, by just following the branch of the metadata as in the table below, and select the last metadata name, for example: Data > customer > first_name (select “ first_name “if you want to map this metadata) 

Example of field mapping table:  

This field mapping table will be found in our app documentation according to the Trigger or Method. 

Select from Default Value Copy Link

If the data is pre-defined, like a status or category, you can choose from a list of options displayed dynamically.

Manually Input Value Copy Link

Need to set a specific value for the field? You can enter it directly in the manual input field by clicking on the lightning bolt icon, or couple it with a flow input (preloaded data from Trigger or Method) by typing “@”. In the list that appeared, just select the wanted data field to map.

Mapping custom or extra fields Copy Link

Explanation of “⊕ Element” and “⊕ Map” Buttons:

⊕ Element Copy Link

The button is used to add a new single item or repeating group of fields to the mapping structure. The fields are define in Wiresk by default.

Use Case:

• When you want to define a specific property or attribute of an item (e.g., name, price, status, etc.).
• It allows you to directly map a single input field from the data source to a corresponding attribute in the receiving entity.

⊕ Map Copy Link

The button is used to add nested fields (like arrays or objects) to the mapping structure from a datasource (Trigger or Method).

Use Case:

• When dealing with complex data structures, such as groups of modifiers, options, or add-ons, where each group contains multiple attributes (e.g., name, type, minimum, maximum).
• It allows you to map a collection or group of related fields in a structured manner.

Don’t stop here! Copy Link