Quick Configuration of Integration Flows via Import

Operation Entry

Create Data Integration Flow -> Import from Template -> Select Connector -> Download Template -> Upload Excel Files

Template Description

Each sheet defines the field-mapping configuration for one integration flow. You can import multiple integration flows at once. The sheet name becomes the integration flow name.

[1] Source System

Indicates the direction of the integration. Enter “CRM” for CRM -> Third Party; enter the third-party system name for Third Party -> CRM.

[2] CRM Object Information

Provide the CRM object and fields to be integrated. The object’s ApiName and the field ApiName are required.

If you need to map Sub-object fields, enter the Primary Object fields first, then list the Sub-object fields below in order. Note that the Primary Object must be provided.

[3] Third-Party Object Information

Required fields: Object Name, Object Code, Field Name, Field Code, Field Type, Is Required. Note that “Object Code” refers to the third-party object code, not the intermediate object Code.

For field types of single-select, multi-select, Lookup Relationship, or Lookup Relationship (multi-select), you must also provide extended information.

If you need to map Sub-objects, likewise enter the Primary Object fields first, then list Sub-object fields below.

System execution logic:

The system first checks whether the third-party object already exists under the selected connector based on the Object Code:

• If it does not exist, the system will create the object and then create the fields;
• If it exists, the system will not create or update the object. It then checks fields by Field Code: if a field does not exist it will be created; if it exists it will not be updated;

• For detail objects, the system creates them as first-level Sub-objects of the Primary Object by default;

• Extended information
• Example format for single-select/multi-select options: [{“value”:”option1_code”,”label”:”option1_label”},{“value”:”option2_code”,”label”:”option2_label”},{“value”:”option3_code”,”label”:”option3_label”}]
• For Lookup Relationship / Lookup Relationship (multi-select): provide the intermediate object’s Code

[4] Use a separate sheet for each integration flow. Do not reuse sheet names.

Integration Flow Generation Logic

If the connector does not yet have the third-party object, the system automatically creates the third-party object and fields.

If the third-party object already exists under the connector, the system fills in any missing fields.

The template generates the following integration flow attributes: Integration Flow Name, Source System, Source Object, Target System, Target Object.

If the direction is Third Party -> CRM, the default trigger action is: Query (every 6 minutes by minute from 00:00 to 23:59). Default execution actions are: Create, Update, Void.

If the direction is CRM -> Third Party, the default execution actions are: Create, Update.

Default status: Disabled

Validation Notes:

If an integration flow with identical Source Object and Target Object already exists, the system will not create or update another flow. We recommend deleting the existing flow before re-importing.

Enumerated types such as single-select will not have option-value mapping performed.

After import completes, adjust object fields and integration flow configuration as needed.