Two-way sync
Changes in Azure Synapse Analytics or Gatekeeper instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Synapse Analytics and Gatekeeper in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Whatever Gatekeeper is used for, it accumulates data the rest of the company wants to analyze, and that data usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay for it.
Stacksync syncs Workflow form data, Custom data groups, Users, Categories from Gatekeeper into tables in Azure Synapse Analytics continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in Azure Synapse Analytics can also be written back into fields in Gatekeeper where the tool can use them.
Combine Gatekeeper's data with data from every other synced system to answer questions no single tool can.
Segments, scores, or reference values computed in Azure Synapse Analytics sync back onto records in Gatekeeper, putting analysis where the work happens.
A continuously synced copy in Azure Synapse Analytics preserves a queryable record even as data ages out of Gatekeeper or gets changed inside it.
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.
| Azure Synapse Analytics objects | Gatekeeper objects | How this pairing syncs | |
|---|---|---|---|
| Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | Custom data groups Customer-configured custom fields and data groups; because the JSON:API and its docs are dynamic, any custom data added in Configuration exposes the same read/write endpoints as the standard objects and syncs the same way. | Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Custom data groups to Gatekeeper — each maps to any object or custom field on the other side. | |
| External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. | Users Gatekeeper user and team records governed by role-based access; read to map contract and vendor owners, approvers, and internal contacts to CRM or HR records. | External tables is specific to Azure Synapse Analytics and Users to Gatekeeper — each maps to any object or custom field on the other side. | |
| Views Curated projections used when downstream tools should not read base tables directly. | Categories The classification taxonomy applied to contracts and vendors (type, department, business unit); synced so categorization stays consistent between Gatekeeper and downstream reporting or ERP dimensions. | Views is specific to Azure Synapse Analytics and Categories to Gatekeeper — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that separate staging, integration, and presentation layers. | Contracts The core contract records holding value, key dates, renewal terms, status, type, owner, and the linked vendor; created, read, updated, and deleted so contract data moves two-way between Gatekeeper and a database, ERP, or CRM. | Schemas is specific to Azure Synapse Analytics and Contracts to Gatekeeper — each maps to any object or custom field on the other side. | |
| Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | Vendors (Suppliers) Company records for counterparties and suppliers with onboarding status, compliance, risk, contacts, and spend; read and written to keep vendor master data aligned with a CRM or ERP. | Materialized views is specific to Azure Synapse Analytics and Vendors (Suppliers) to Gatekeeper — each maps to any object or custom field on the other side. | |
| SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | Files Document files attached to contracts and vendors - executed PDFs, certificates, and compliance evidence; read to pull signed files and evidence out, or written to push generated documents in. | SQL pools is specific to Azure Synapse Analytics and Files to Gatekeeper — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.
DeliveryEach detected change is written to Gatekeeper through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Gatekeeper for changes on an incremental schedule, reading only records changed since the previous pass. No native developer webhook subscription API and no database change-data-capture log.
DeliveryEach detected change is applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Gatekeeper connection.
Changes in Azure Synapse Analytics or Gatekeeper instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Synapse Analytics or Gatekeeper data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Synapse Analytics or Gatekeeper record.
Track your Azure Synapse Analytics ⇄ Gatekeeper sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Gatekeeper.
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 Azure Synapse Analytics and Gatekeeper 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 Azure Synapse Analytics and Gatekeeper 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 two-way integration between Azure Synapse Analytics and Gatekeeper: authenticate both systems, choose the objects to sync (such as Azure Synapse Analytics's Tables (dedicated SQL pool) and External tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Azure Synapse Analytics: Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers. On Gatekeeper: No native developer webhook subscription API and no database change-data-capture log; detect changes by polling the JSON:API list endpoints filtered and sorted on updated-at timestamps. Gatekeeper's own event automation - Workflow Engine phase transitions and Interconnect process orchestration - runs inside the platform rather than as a subscribable webhook stream. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Gatekeeper side: Workflow form data, Custom data groups, Users, Categories, plus custom fields where Gatekeeper exposes them. On the Azure Synapse Analytics side: Schemas, Materialized views, SQL pools, Tables (dedicated SQL pool). Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Azure Synapse Analytics and Gatekeeper: Cross-tool reporting; Where Gatekeeper accepts updates: operational write-back; History that outlives the tool. Combine Gatekeeper's data with data from every other synced system to answer questions no single tool can.
Azure Synapse Analytics: SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint. Authentication: SQL authentication or Microsoft Entra ID. Gatekeeper: RESTful API following the JSON:API specification, tenant-scoped with interactive docs at {tenant}.gatekeeperhq.com/api_docs and a published Postman collection. The API is dynamic: it exposes the standard Contract and Vendor objects plus any custom data groups and workflow-form data configured in the tenant. Authentication: API keys created and managed under Configuration > API Keys and passed as a token; each key carries granular per-endpoint permissions set to read-only or write, so access is scoped per object. Multiple keys can be issued and revoked independently. 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 442 integrations available for Azure Synapse Analytics and Gatekeeper.