Skip to content
Storage ⇄ Database

Egnyte to Reltio integration — real-time, two-way sync

Keep Egnyte and Reltio 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 Egnyte and Reltio

Keep Reltio and Egnyte in step: a row in Reltio for every file in Egnyte, with names, paths, metadata, and status staying consistent in real time, in both directions.

A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in Reltio says a file exists and carries its name, location, and status, while Egnyte holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.

Stacksync syncs Activity Log, Data Change Requests (DCR), Reference Data (RDM), Entities in Reltio with Links, Metadata, Events and Audit reports, Files in Egnyte bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.

Common use cases

  • 01 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
  • 02 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
  • 03 Mirror folder Permissions from a directory or access-management system so entitlements stay consistent across teams.
  • 04 Stream Egnyte audit Events (file, login, permission, and Link changes) into a warehouse or SIEM for compliance and governance reporting.

Common sync patterns

A queryable index of the file store

Every file or object in Egnyte shows up as a row in Reltio, with its name, folder or key, size, type, and modified date as columns, so the contents of the store can be listed, filtered, and joined like any other table.

File metadata kept in step

Tags, custom properties, owner, or status columns edited on a row in Reltio write back to the matching file's metadata in Egnyte, and metadata changed in Egnyte updates the row, so the two never disagree about a file.

Records that point at documents

Where a record in Reltio references a file in Egnyte, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.

What you can sync between Egnyte and Reltio

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.

Egnyte objects Reltio objects How this pairing syncs
Groups Groups and membership managed via the Groups API; kept aligned with directory or IdP groups that drive folder access. Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Groups is specific to Egnyte and Relations to Reltio — each maps to any object or custom field on the other side.
Permissions Folder permissions listed, set, and removed via the Permissions API; effective permission for a user/folder is computable. Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Permissions is specific to Egnyte and Crosswalks to Reltio — each maps to any object or custom field on the other side.
Links Shared file and folder links created, listed, and revoked via the Links API; useful for governing and auditing external sharing. Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Links is specific to Egnyte and Interactions to Reltio — each maps to any object or custom field on the other side.
Metadata Custom metadata keys and project fields on files/folders via the Metadata API; written for classification and read back for reporting. Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Metadata is specific to Egnyte and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side.
Events and Audit reports File, login, permission, and sharing activity read via the Events API and Audit Reporting API; consumed read-only for compliance. Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Events and Audit reports is specific to Egnyte and Activity Log to Reltio — each maps to any object or custom field on the other side.
Files File content managed via the fs-content endpoint (upload/download, chunked for large files); synced two-way with other stores. Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Files is specific to Egnyte and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side.

How changes propagate between Egnyte and Reltio

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.

Egnyte Reltio Sub-second propagation

DetectionEgnyte notifies Stacksync of record changes through webhook events. Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata,.

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

Reltio Egnyte Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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

Rate-limit considerations

  • Egnyte: Auto-generated keys default to 2 requests/second and 1,000 requests/day, enforced per access token; monitor X-Accesstoken-Qps-Current/Allotted and X-Accesstoken-Quota-Current headers; higher limits on request.
  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Egnyte ⇄ Reltio

Connect Egnyte and Reltio for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Egnyte or Reltio instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Egnyte or Reltio 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 Egnyte or Reltio record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Egnyte and Reltio.

How the Egnyte and Reltio connectors work

Egnyte

Integration surface
REST Public API (pubapi/v1) with File System, Users, Groups, Permissions, Links, Metadata, Events, and Webhooks endpoints
Authentication
OAuth 2.0 scoped access tokens (Authorization Code or Implicit for partner apps, Resource Owner Password for internal apps, Refresh Token flow); token sent in the Authorization header
Change detection
Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata, permission, and comment events
Capabilities
read · write · webhooks
Rate limits
Auto-generated keys default to 2 requests/second and 1,000 requests/day, enforced per access token; monitor X-Accesstoken-Qps-Current/Allotted and X-Accesstoken-Quota-Current headers; higher limits on request

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works

How to connect Egnyte to Reltio — 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 Egnyte and Reltio 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
    Egnyte connected
    Reltio connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Egnyte and Reltio 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 · Egnyte ⇄ Reltio
    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
    Egnyte Reltio
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Egnyte and Reltio 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
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 422 integrations available for Egnyte and Reltio.

Popular · 7 of 422
All Egnyte integrations All Reltio 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