Etlworks terminology

Connection - a way to connect to external data sources. In order to perform data integration operations, you first need to create a connection.

Connector - a type of connection, such as a Database Connector, Twitter Connector, etc.

Listener - a special type of connection which is "listening" for a specific event. For example, an inbound HTTP request, which then triggers the execution of data integration flows. Listeners allow the user to create event-driven flows.

Format - a data exchange format, such as CSV, JSON, Excel, etc. When data objects are involved, when working with web services or files for example, you need to describe all the formats required for the data exchange.

Flow - a data integration flow, which combines one or more transformations.

Event-driven flow - flow executed when a certain event occurs and the listener receives an event.

Schedule - a way to automatically execute flows, based on pre-configured time intervals.

Source-to-destination transformation - the most common transformation. Etlworks Integrator extracts data from the source, transforms it and loads it into the destination. 

Source - the FROM part of a source-to-destination transformation.

Destination - the TO part of a source-to-destination transformation.

Mapping - the mapping between fields in the source and fields in the destination.

High-level transformation - a transformation of the entire dataset, which is performed as a single operation, for example, deduplication.

Dimension - the inner dataset in a complex data object.

Well-known API - the business application or API for which Etlworks has a native connector, for example, Marketo, Salesforce, etc.

Parametrization - a way to dynamically configure connections and transformations based on input parameters. The input parameters can be Global variables or Flow variables.

Global variables - key-value pairs that are set either by JavaScript code or are automatically set when running flows.

Flow variables - key-value pairs that are passed as URL parameters in the user-created API endpoints or added by the user as parameters in the nested flow.

Key/value storage - a common facility for objects, programmatically stored as key/value pairs and accessible from anywhere within the JavaScript. Unlike global variables and flow variables, you can add any object to the key/value storage.