On this page
translate
Glossary
Definitions of terms and concepts used throughout IMSURGE.
This glossary defines the core concepts and terminology used in IMSURGE. Familiarity with these terms will help you understand the documentation more quickly.
| Term | Definition |
|---|---|
| Credentials | A secure IMSURGE object that stores the authentication details (API keys, usernames, tokens) required for an integration to access an external system. Credentials can be reused across multiple integrations and pipelines. |
| Vendor Credentials | The authentication details required by an external platform itself (such as a vendor’s API key, username, or password). These values are entered into IMSURGE when creating a set of Credentials. |
| Integration | A configured connection to a vendor system. A source integration collects data; a target integration delivers data. Integrations use Credentials for authentication. |
| Pipeline | A scheduled workflow that connects one source integration to one target integration. |
| Execution | A record of each pipeline run, including status (success, warning, failure), event files, metadata and any error messages |
| Execution Event | An action recorded during an execution, detailing specific steps or occurrences (such as data retrieval, transformation, or delivery) within that run. |
| Pipeline Source | The upstream device or system from which IMSURGE collects data. |
| Pipeline Target | The downstream destination where IMSURGE sends processed pipeline data. |