How to Use Last Time Expression in ZigiOps

In today’s video, we’ll walk you through how to use expressions in integrations — and more specifically, the Last Time Expression, one of the most commonly used features in ZigiOps.

ZigiOps is a powerful no-code data integration platform that helps you connect and synchronize ITSM, DevOps, monitoring, and CRM systems. The Last Time expression is essential for avoiding data duplication and optimizing performance in your bi-directional integrations.

Step 1: What Are Expressions in Integrations?

Expressions are used to define additional variables by modifying or extending existing data extracted from the source system. This allows you to create values and triggers not originally provided by the system.

Step 2: Why Use the Last Time Expression?
‍

The Last Time Expression ensures that only new records are collected from the source system, avoiding duplication. It stores the latest value (like a timestamp or numeric ID), so future data extractions only include new or updated entities.

Step 3: Setting Up a Last Time Expression in ZigiOps UI

• Navigate to the Source tab of your integration.

• Create a variable (e.g., lastCreated or lastUpdated).

• Select the appropriate source field (a date/time or number field like systemCreatedDate).

• The expression will track the largest value encountered to determine what's new.

Step 4: Define Trigger Conditions

Once your variable is set, you can use it in your trigger logic. For example:
systemCreatedDate > lastCreated
This ensures only new tasks or incidents are processed.

Step 5: Handling Load Errors
‍

If a data load fails, ZigiOps offers control over whether to increment Last Time:

• For network errors, Last Time is not incremented, allowing retries.

• For other errors (e.g., 404 from a deleted Jira ticket), Last Time is incremented to prevent infinite loops.

Step 6: Execution and Validation
The expression is validated after the response is received — not at data extraction. This helps avoid premature filtering and ensures accurate correlation.

Step 7: Use Case Examples

• Azure DevOps – ServiceNow Integration: Use separate Last Time expressions for issues, comments, and attachments to track and sync them independently.

• Nagios – OBM Integration: Track the latest metrics and sync only new ones.

• Topology Integrations: Do not use Last Time here, as full syncs are preferred.

Why It Matters for Your Integration Strategy

• Avoids duplicate records across systems

• Speeds up data processing by focusing only on new information

• Essential for real-time, bi-directional integration

• Fully customizable based on your use case

• Works across a wide range of ITSM, DevOps, and monitoring tools

If you're using or planning to use a data integration platform like ZigiOps and want to ensure efficient and accurate data synchronization, this feature is a must-know.

Book a technical demo today or start your free trial. Let our team show you how to configure the Last Time Expression for your specific needs.