Skip to content
ERP ⇄ Business productivity

Cin7 to Gatekeeper integration — real-time, two-way sync

Keep Cin7 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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Cin7 and Gatekeeper

Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Gatekeeper and Cin7.

The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Gatekeeper is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.

Stacksync syncs Users, Categories, Contracts, Vendors (Suppliers) in Gatekeeper with Contacts, Branches / locations, Stock adjustments and transfers, Credit notes / returns in Cin7 bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.

Common use cases

  • 01 Write contract or vendor records into Gatekeeper when a deal closes in the CRM to kick off downstream procurement and legal workflows.
  • 02 Two-way sync Contracts between Gatekeeper and an ERP or warehouse so value, renewal dates, owner, and status stay current without manual re-keying.
  • 03 Keep customer records aligned between Cin7 and the CRM to remove duplicate account entry.
  • 04 Write purchase orders created in a planning tool back into Cin7 for receiving.

Common sync patterns

Where Cin7 is the HR or people system of record

Worker and organization data from Cin7 stays current in Gatekeeper, so the tools people use daily reflect the org as it actually is.

Master data corrections travel

A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.

Where Gatekeeper faces customers and Cin7 carries account records

Order, invoice, or account status from Cin7 appears alongside the customer in Gatekeeper, so front-line teams answer from live data.

What you can sync between Cin7 and Gatekeeper

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.

Cin7 objects Gatekeeper objects How this pairing syncs
Inventory levels Stock on hand by branch or location, published outward for availability. 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. Inventory levels is specific to Cin7 and Vendors (Suppliers) to Gatekeeper — each maps to any object or custom field on the other side.
Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. 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. Sales orders is specific to Cin7 and Files to Gatekeeper — each maps to any object or custom field on the other side.
Purchase orders Supplier orders synced with procurement and accounting workflows. Workflow form data The structured data captured on Gatekeeper workflow forms (intake requests, vendor onboarding, risk assessments); exposed by the API since 2025 so form results sync into an operational database, not only contract and vendor records. Purchase orders is specific to Cin7 and Workflow form data to Gatekeeper — each maps to any object or custom field on the other side.
Contacts Customers and suppliers, matched to CRM records to keep account data consistent. 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. Contacts is specific to Cin7 and Custom data groups to Gatekeeper — each maps to any object or custom field on the other side.
Branches / locations Warehouse entities that scope every stock movement and order allocation. 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. Branches / locations is specific to Cin7 and Users to Gatekeeper — each maps to any object or custom field on the other side.
Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. 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. Stock adjustments and transfers is specific to Cin7 and Categories to Gatekeeper — each maps to any object or custom field on the other side.

How changes propagate between Cin7 and Gatekeeper

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.

Cin7 Gatekeeper Sub-second propagation

DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.

DeliveryEach detected change is written to Gatekeeper through its API, with automatic retries and rate-limit backoff.

Gatekeeper Cin7 Interval-based propagation

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 written to Cin7 through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
  • Gatekeeper: Gatekeeper publishes no fixed public per-minute request quota; throughput is governed per key by its endpoint permissions, and every call is recorded (parameters, payload, response) under API Logs for monitoring. Pace bulk writes and use JSON:API pagination on list endpoints.
What ships with Cin7 ⇄ Gatekeeper

Connect Cin7 and Gatekeeper for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cin7–Gatekeeper connection.

Real-time

Two-way sync

Changes in Cin7 or Gatekeeper instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Cin7 or Gatekeeper data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Cin7 or Gatekeeper record.

Observability

Monitoring

Track your Cin7 ⇄ Gatekeeper sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Cin7 and Gatekeeper.

How the Cin7 and Gatekeeper connectors work

Cin7

Integration surface
REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
Authentication
API key credentials (paired with a username or account ID, depending on the product)
Change detection
Polling on modified-date filters; webhook support exists on some editions for order and stock events
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core

Gatekeeper

Integration surface
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.
Change detection
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.
Capabilities
read · write
Rate limits
Gatekeeper publishes no fixed public per-minute request quota; throughput is governed per key by its endpoint permissions, and every call is recorded (parameters, payload, response) under API Logs for monitoring. Pace bulk writes and use JSON:API pagination on list endpoints.
How it works

How to connect Cin7 to Gatekeeper — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Cin7 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Cin7 connected
    Gatekeeper connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Cin7 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Cin7 ⇄ Gatekeeper
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Cin7 Gatekeeper
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Cin7 and Gatekeeper integration FAQ

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 401 integrations available for Cin7 and Gatekeeper.

Popular · 6 of 401
All Cin7 integrations All Gatekeeper integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own