Real-time sync
Changes in InterSystems IRIS or Lusha instantly reflect in both systems. No stale data, no manual imports.
Keep InterSystems IRIS and Lusha in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Lusha is a read-only source: Stacksync reads its data in real time and delivers it into InterSystems IRIS, so InterSystems IRIS always reflects the current state of Lusha — without exports, scripts, or schedulers.
Engineers integrate with tools like Lusha through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in InterSystems IRIS.
Stacksync mirrors Phone Numbers, Prospecting Results, Bulk Enrichment Requests, Person Profiles from Lusha into Persistent Classes, Globals, Namespaces, Stored Procedures in InterSystems IRIS and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Lusha, so the tool and the database never disagree.
Updates in Lusha arrive as row changes in InterSystems IRIS, so triggers, jobs, and services can respond in near real time.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Records from Lusha are ordinary rows in InterSystems IRIS; join them, index them, and use them in application logic without touching the vendor API.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| InterSystems IRIS objects | Lusha objects | |
|---|---|---|
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Phone Numbers Direct-dial and mobile numbers appended for outbound calling workflows. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Prospecting Results Search-based lists of people and companies matching filters, used to seed lead lists. | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Bulk Enrichment Requests Batch lookups that enrich multiple records per request, used to backfill large contact lists rather than one-off calls. | |
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Person Profiles Contact-level enrichment results (work emails, phone numbers, title, company) returned per lookup. | |
| Views SQL views expose curated slices of data for outbound replication. | Company Profiles Firmographic records (industry, size, location) appended to account or company rows. | |
| Schemas Schema organization scopes which tables a sync connection can see. | Email Addresses Work emails written into CRM contact fields during enrichment. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Lusha connection.
Changes in InterSystems IRIS or Lusha instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS or Lusha data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single InterSystems IRIS or Lusha record.
Track your InterSystems IRIS ⇄ Lusha sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Lusha.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate InterSystems IRIS and Lusha with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the InterSystems IRIS and Lusha objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time integration between InterSystems IRIS and Lusha — Lusha is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
Change detection on InterSystems IRIS: Polling (timestamp or query-based); no standard webhook surface. On Lusha: Not event-driven; data is fetched on demand per lookup, so syncs poll or trigger enrichment when source records change. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Lusha side: Phone Numbers, Prospecting Results, Bulk Enrichment Requests, Person Profiles, plus custom fields where Lusha exposes them. On the InterSystems IRIS side: Persistent Classes, Globals, Namespaces, Stored Procedures. Stacksync auto-detects both schemas and converts types between the two systems.
Lusha is a read-only source, so this integration runs one-way: Stacksync reads from Lusha in real time and delivers into InterSystems IRIS. Field mapping and monitoring work the same as for two-way pairs.
Common patterns for InterSystems IRIS and Lusha: React to changes as they happen; One integration pattern for the whole stack; Read Lusha with a query. Updates in Lusha arrive as row changes in InterSystems IRIS, so triggers, jobs, and services can respond in near real time.
InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. Lusha: REST API. Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for InterSystems IRIS and Lusha.