# ZigiOps Terminology
**A. Core Integration Concepts**
#### Workflow
The main entity users work with in ZigiOps.\
The workflow represents a goal (or use case) that needs to be achieved by the customer.\
It contains all the configuration and logic for systems, correlation, actions, filters, mappings, conditions that are required for achieving a use case.
\
A workflow is defined by a pair of systems and the type of data which will be used, for example:\
• jira\_production task ↔︎ servicenow\_production incident\
• solarwinds\_test alert → operations\_bridge\_test event
#### Workflow Template
A predefined workflow blueprint that includes mappings, triggers, and actions for a specific system pair.
### System
The system describes what ZigiOps can connect to, for example “System: Jira” means that ZigiOps has the capability to connect and integrate with Jira systems.
#### System Instance
This represents the actual connection between ZigiOps and a system. It contains the configuration that describes the connection, like name, url, authentication, proxy, etc.
\
Examples:\
• System Instance: new-jira-1 with url [https://jira1.atlassian.com](https://jira1.atlassian.com/)\
• System Instance: new-jira-2 with url [https://jira2.atlassian.com](https://jira2.atlassian.com/)
#### System Entity
This is the type of data which will be used for a particular System Instance as part of a workflow.
\
Examples:\
• new-jira-1 with entity: TEST.task\
• new-snow-1 with entity: incident
#### System Pair
The two connected systems involved in an integration (e.g., ServiceNow ↔ Jira).
### Correlation
Correlation is a feature of every workflow and defines where ZigiOps will store unique key information which can be used for synchronizing updates between records in both directions. Correlation information can be stored in the Source system, Target system or in both at the same time.
ZigiOps uses that information during update actions to validate what is the correct entity that needs to be updated.
\
Common Examples:\
• ServiceNow uses the default “correlation\_id”\
• Jira uses a dedicated custom field\
• Remedy uses “Vendor Ticket Number”
### Integration
The automated connection between two systems that enables data exchange based on a defined workflow.
#### Custom Integration
A manually created integration, configured from scratch using the ZigiOps UI.
### B. Data Mapping Concepts
#### Transformation
A function applied to data during mapping (e.g., format change, prefix, concatenation).
#### Lookup
A mechanism for retrieving a related value from the target system based on a source field.
#### Correlation Field
A field used to maintain a unique link between related records across systems.
#### Static Value Mapping
A constant assigned to a field during sync (e.g., “priority = 3”).
#### Dynamic Value Mapping
Field values determined at runtime based on source fields.
#### Attachment Sync
The process of transferring file attachments between systems.
#### Comment / Journal Sync
Synchronizing comments, work notes, or journal entries.
### Field Mapping
Field mappings are used to specify what data is going to be delivered to the target system of the action. Values may be source fields, hardcoded strings, or combinations.
\
Examples:\
summary = {short\_description}\
summary = {number}: {short\_description}\
comments/body = {comments/body}
#### Field Mapping Conditions
Conditional mappings define when a certain field should be reported or how values change based on specific criteria.\
Examples include lifecycle conversions or conditional reporting.
**Respond Field Mapping**
Mapping from the target system back to the source system.\
Commonly used to create comments that contain confirmation or drilldown links.
### C. Execution Mechanisms
#### Poller
The mechanism that periodically checks a source system for changes.
#### Web Listener
A listener that receives event-based data from monitoring or DevOps tools.
#### Bulk Transfer
The ability to transfer large batches of records in a single request.
#### Retry Logic
A built-in mechanism for automatically reattempting failed actions.
#### Action
The component within a workflow that directly works with data.\
A workflow may contain multiple actions such as Create, Update, or Sync operations.
#### Source
Where data is collected from. Includes filters, triggers, related filters, expressions, lasttime, and more.
#### Target
The destination system where the action delivers data.\
Each action defines its own target configuration, including mappings and conditions.
#### Trigger
Defines when an action is executed:\
• poller – runs on a timed interval\
• web listener – fires immediately on incoming data
#### Filter
Specifies which records should be collected.
Related Filter
Used to collect related records such as attachments or comments.
### D. API & Authentication
#### API Token
A secret token used to authenticate ZigiOps against the system API.
#### Personal Access Token (PAT)
Authentication mechanism used by tools like Azure DevOps and Jira Cloud.
#### Client ID / Client Secret
OAuth-based credentials used for authentication.
#### Bearer Token
Authentication token added to HTTP headers.
#### Basic Authentication
Username + password (or token) authentication.
#### REST API
The standard interface ZigiOps uses to communicate with integrated systems.
#### Webhook
A mechanism that allows an external system to send data to ZigiOps in real time.
#### MCP (Model Context Protocol)
MCP protocol that allows ZigiOps to expose systems directly to ChatGPT or AI models.
### E. System Configuration Terms
#### Proxy Settings
Configuration allowing ZigiOps to route traffic through a proxy server.
#### MID Server
A ServiceNow component that facilitates secure communication with external systems.
#### Listener URL
The endpoint where ZigiOps receives incoming data from systems such as Dynatrace, Azure Monitor, or SAP SolMan.
#### Instance Type
Defines whether a system is Cloud, Server, SaaS, etc.
#### Server URL
Base URL of the connected system used for API communication.
#### Management Pack / Connector
Additional components required by certain systems (e.g., vROps).
#### License
The license allows the user to enable the automation for workflows and actions. It is bound by a pair of systems and number of points.
### F. Error Handling & Troubleshooting Terms
#### Error Log
A log of failures, exceptions, or rejected records generated by ZigiOps.
#### Permission Error
An error caused by insufficient access rights.
#### Authentication Failure
A failure due to incorrect credentials or expired tokens.
#### Transformation Error
An issue caused by a mapping or expression.
#### Payload
The JSON body sent to or from a connected system during integration.
### G. Platform Architecture Terms
#### Integration Hub
The core engine running ZigiOps integrations.
#### Runtime Files
Files generated during operations (logs, temporary data, etc.).
#### Scaling & Load
How ZigiOps handles volume, concurrency, and heavy workloads.
HA (High Availability)
Multi-node setup for reliability.
Network Storage
External storage for runtime files in HA deployments.
### H. ZigiOps UI Terms
#### Configurator
The main UI section for building and modifying integrations.
#### Dashboard
The overview screen showing system health and integration status.
#### Activity Log
A record of executed actions, polling cycles, and listener events.
#### System Instances
The list of configured connected systems.
#### Accessible by AI
The toggle enabling MCP exposure for a specific system instance.
#### Mapping Table
UI interface for field-to-field mappings.
#### Condition Builder
UI tool for constructing logical conditions and filters.
#### I. Security & Compliance Terms
* Encryption at Rest
* Encryption of stored data.
* Encryption in Transit
* HTTPS/TLS encryption during communication.
* ISO 27001
* Security certification.
* Hardening
* Security configurations that restrict access and strengthen defenses.
### J. Expressions & Transformations
#### Expressions
Expressions are used for additional data transformations after data collection and before delivery to the target system. They may be reused inside field mappings.
**Expression: Pattern**
Allows regex-based data extraction or modification.
* Expression: Extract from Array
* Extracts a specific object from an array.
**Expression: Build Array**
* Combines multiple values into an array using a separator.
**Expression: To Lower Case**
* Converts text to lowercase.
**Expression: To Upper Case**
* Converts text to uppercase.
**Expression: First N Characters**
* Trims text to the first N characters.
**Expression: Last N Characters**
* Trims text to the last N characters.
**Expression: Replace Text**
* Replaces specified text with another text.
**Expression: Replace Pattern**
* Uses regex to replace matched patterns.
**Expression: Date and Time Format**
* Converts timestamps to human-readable formats.
**Expression: Last Time**
* Records the latest timestamp of collected data to avoid duplicates.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.zigiwave.com/integration-platform/zigiops-terminology.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.