Glossary of Coupler.io Terminology
This article is aimed at helping you understand and familiarize yourself with Coupler.io’s terminology.
| Term | Definition | Useful Links |
|---|---|---|
| Data flow | An integration you set up in Coupler.io that brings data from your selected source(s) into your chosen destination(s). In each Coupler.io data flow, you define what dataset you want to pull, from where, to where, if/how often it needs to be automatically updated, etc. | |
| Source/ Data source | An application you pull data from. | Data sources supported by Coupler.io: https://www.coupler.io/sources How to extract data from supported sources: |
| Destination/ Data destination | An application you pull data into. | Data destinations supported by Coupler.io: https://www.coupler.io/destinations How to pull data to the supported destinations: |
| Connection | A data connection in Coupler.io is defined by the interaction between a data flow and the source application, along with the specific account being accessed. Each unique combination counts as a separate connection. | What is a Data Connection |
| Run | The execution process of a data flow. After setting up the data flow, "run" is the action that triggers it to make a call to your source app and pull data from it to your destination app. Runs can be: - manual (when you manually press the "run" button of your data flow) - automatic (when the data flow runs automatically according to the schedule you set up). |
|
| Import | The process of writing data to the destination. | |
Replace(import mode) |
An approach Coupler.io uses when uploading your data to the destination. When you run a data flow in the replace mode, all the previously imported data is removed from your destination, and the current run's data replaces it. | Replace vs append import mode |
| Append(import mode) | An approach Coupler.io uses when uploading your data to the destination. When you run a data flow in the append mode, all the previously imported data remains in your destination, and the current run's data is added below it. Note: current run's data means all the data Coupler.io grabs from your source app(s), matching current parameters, settings, and transformations you applied to the data flow. |
Replace vs append import mode |
| Transformations | A step during a data flow setup where you can preview and transform your original source data before further importing it to the destination. | Detailed description of what transformations can be applied to data: Preview data and transformation |
| Data combining/Data merging | Combining data from multiple sources into a unified dataset with one data flow. Data can be combined using different modes: Join, Append. |
Combining data from multiple sources
|
| Join(data combining mode) | Data combining mode that merges two or more sources using LEFT JOIN (from SQL terminology). Similar to VLookup function. When Join mode is used for combining data, all the elements from the left dataset are kept, while only the matching elements from the right dataset are included. |
|
| Append(data combining mode) | The process of combining values from two or more data sets and placing them under the same column(s) in the destination file. Append data combining mode stitches two or more sources placing data from each source one below another. With this mode, Coupler.io compiles the list of unique column names from all the sources it’s meant to stitch. It then puts all data under these columns, using their names as identifiers and keeping rows' content as it was in the sources. |
Data Append |
| Formula-based column/ calculable column | A Transformations feature that allows adding a formula-based column to your original dataset. Mostly used for calculating custom values based on existing data. | Adding formula-based custom columns |
| Runs limit [legacy] | A billing limit of Coupler.io that defines the total number of times you can run your importers per month. Every time an importer is run (either manually or automatically) is counted towards this limit. | How does Coupler.io calculate runs limits |
| Max import size limit [legacy] | A billing limit of Coupler.io that defines how many rows you can pull with your data flow per run. | How does Coupler.io calculate max import size limit Data was partially imported because you have exceeded your current plan limit |
| Connections limit | A billing limit of Coupler.io that defines how many data connections you may have in your billing plan. | How does Coupler.io calculate Data Connections? |
| Metered sources | Data sources that have a Data Volume limit. | Metered Sources |
Haven't found the term you were looking for? Reach us at contact@coupler.io, and we'll get it covered!