If you need to import profiles, events, transactions of external sources or to retrieve a group of customers for further actions, you may use the nodes below for these purposes.

### Import nodes overview
---

#### Import Profiles
This node allows you to initiate an import of profiles to Synerise. The node doesn't require any configuration.

To learn more, click [here](/docs/automation/actions/synerise-integrations/import-customers).

#### Import Transactions
This node allows you to initiate an import of transactions to Synerise. The transactions are imported as `transaction.charge` events into a profile's history.  
In the configuration of the node, you can find a list of required columns in the imported file.   
You can also use the option of automatic revenue calculation. To do so, you must first indicate the column which contains the price of a single piece of the item. Then, during import, the system aggregates data based on the `orderId` and multiplies the single piece price by the quantity bought. The result of the calculation will be saved in the `revenue.amount` and `revenue.value` parameters of the `transaction.charge` event.

To learn more, click [here](/docs/automation/actions/synerise-integrations/import-transactions).

#### Import Events
This node allows you to initiate an import of events to Synerise. The node doesn't require any configuration.

To learn more, click [here](/docs/automation/actions/synerise-integrations/import-events).

#### Import Promotions
This node allows you to initiate an import of promotions to Synerise. The node doesn't require any configuration.

To learn more, click [here](/docs/automation/actions/synerise-integrations/import-promotions). 

#### Import to Catalogs

This node initiates the import of data to a catalog created in **Data Modeling Hub > Catalogs**. The catalog can be empty. 

In the configuration of the node:
1. Select the catalog to which the file will be imported.  
2. As the primary key, enter the name of the column which contains the unique identifiers of the items.
3. Confirm by clicking **Apply**. 

To learn more, click [here](/docs/automation/actions/synerise-integrations/import-to-catalog).

### Example with transformation
---

<figure>
<img src="/api/docs/image/54176ad07f146575310749eba44b7c2f42c1b327/docs/automation/_gfx/import-with-data-transformation.png" alt="Example of use" class="full">
<figcaption>Single import of transactions to Synerise</figcaption>
</figure>

#### When to use 
If the files you want to import to Synerise don't meet the requirements, you can create a [data transformation](/docs/automation/data-transformation-and-imports/creating-data-transformation) and use it in the Data Transformation node.

#### Workflow structure
1. [Scheduled Run node](/docs/automation/triggers/scheduled-run) - This node allows you to define the frequency of importing the file.
2. [Local File node](/docs/automation/operation/local-file-node) - This node allows you to upload a file from your device to be modified. You can also upload data through [SFTP](/docs/automation/integration/sftp-integrations) or [HTTP](/docs/automation/integration/http-integrations).
3. [Data Transformation node](/docs/automation/operation/data-transformation-node) - This node allows you to prepare your file to meet Synerise requirements.
4. Import nodes - The scope of the nodes include: **Import Profiles**, **Import Transactions**, **Import Events**, **Import to Catalog**. These nodes don't require configuration, they list the requirements for the files to be imported. 
5. The **End** node.

### Example without transformation
---

<figure>
<img src="/api/docs/image/54176ad07f146575310749eba44b7c2f42c1b327/docs/automation/_gfx/local-file-example-of-use.png" alt="Example of use" class="full">
<figcaption>Single import of customers to Synerise</figcaption>
</figure>


<div class="admonition admonition-important"><div class="admonition-icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2.5"><path stroke-linecap="round" stroke-linejoin="round" d="M12 8v4m0 4h.01M21 12a9 9 0 11-18 0 9 9 0 0118 0z" /></svg></div><div class="admonition-body"><div class="admonition-content">

The data will be imported as customer data without any transformation.

</div></div></div>


#### When to use   
If the file you want to import to Synerise meets the requirements, you don't need to use the Data Transformation node.

#### Workflow structure
1. [Scheduled Run node](/docs/automation/triggers/scheduled-run) - This node allows you to define the frequency of importing the file.
2. [Local File node](/docs/automation/operation/local-file-node) - This node allows you to upload a file from your device. You can also upload data through [SFTP](/docs/automation/integration/sftp-integrations) or [HTTP](/docs/automation/integration/http-integrations).
3. Import nodes - The scope of the nodes include: [Import Profiles](/docs/automation/actions/synerise-integrations/import-customers), [Import Transactions](/docs/automation/actions/synerise-integrations/import-transactions), [Import Events](/docs/automation/actions/synerise-integrations/import-events), [Import to Catalog](/docs/automation/actions/synerise-integrations/import-to-catalog). These nodes don't require configuration, they list the requirements for the files to be imported. 
4. The **End** node.