Two-way sync
Changes in Full Enrich or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Keep Full Enrich and Sharepoint in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Full Enrich and Sharepoint hold different kinds of data. Full Enrich carries records and the activity around them — the tickets, messages, orders, or issues a team works through, often with documents attached. Sharepoint holds files and the metadata that describes them. Where the two meet is narrow but real: much of what Full Enrich produces has to be kept somewhere durable, and many of the files Sharepoint stores are the very documents Full Enrich's records point to.
Stacksync syncs Enrichment requests, Contacts, Enrichment results, Emails in Full Enrich with Sites, Lists, List items, Drive items (document libraries) in Sharepoint in real time. Records and attachments created in Full Enrich are written into Sharepoint as objects or files within seconds of being created. In the other direction, the metadata Sharepoint keeps about those files — name, location, owner, modified date — flows back onto the matching record in Full Enrich, so people see the current document without leaving the tool. Field-level mapping controls exactly what crosses over and in which direction, so you keep a durable copy of what matters without an extract to schedule or a nightly dump that leaves the copy a day behind.
A continuously synced copy in Sharepoint preserves records and documents even as they age out of Full Enrich or get changed inside it, so history stays intact and reachable.
Structured records from Full Enrich land in Sharepoint as objects a data lake, search index, or processing pipeline can read, without a custom extract to build and babysit.
Records and events from Full Enrich — tickets, messages, orders, or issues — are written into Sharepoint as objects or files as they change, giving you a durable, addressable copy for retention and audit.
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.
| Full Enrich objects | Sharepoint objects | How this pairing syncs | |
|---|---|---|---|
| Enrichment results Completed records fetched by request ID or delivered via webhook. | Site pages Modern site pages via /sites/{id}/pages; read page content, layout, and metadata for indexing and content governance. | Enrichment results is specific to Full Enrich and Site pages to Sharepoint — each maps to any object or custom field on the other side. | |
| Emails Returned addresses with verification status, written back to the CRM or database. | Sites SharePoint site collections and subsites via /sites; read site properties and discover the document libraries (drives) and lists each site contains, addressed by hostname and site path or site ID. | Emails is specific to Full Enrich and Sites to Sharepoint — each maps to any object or custom field on the other side. | |
| Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. | Lists Custom lists and libraries via /sites/{id}/lists; create and read lists along with their columns and content types so a target system can mirror or provision list definitions. | Phone numbers is specific to Full Enrich and Lists to Sharepoint — each maps to any object or custom field on the other side. | |
| Credits Account balance consumed on successful finds; monitored to pace sync jobs. | List items Rows in a SharePoint list via /lists/{id}/items with a fields facet of column values; full create, read, update, and delete, synced two-way with database rows. | Credits is specific to Full Enrich and List items to Sharepoint — each maps to any object or custom field on the other side. | |
| Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. | Drive items (document libraries) Files and folders in a library's drive via /drives and /drive/root; upload, download, move, delete, and read per-item metadata, synced two-way with a store. | Enrichment requests is specific to Full Enrich and Drive items (document libraries) to Sharepoint — each maps to any object or custom field on the other side. | |
| Contacts The person inputs (name plus company or domain) sent for enrichment. | Columns and content types Field definitions and content types on a site or list; read the schema and create columns so database fields map cleanly onto SharePoint list fields. | Contacts is specific to Full Enrich and Columns and content types to Sharepoint — 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.
DetectionFull Enrich notifies Stacksync of record changes through webhook events. Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback.
DeliveryEach detected change is written to Sharepoint through its API, with automatic retries and rate-limit backoff.
DetectionSharepoint notifies Stacksync of record changes through webhook events. Delta query (pull) tracks created, updated, and deleted list items (/lists/{id}/items/delta) and drive items (/drives/{id}/root/delta) since the last.
DeliveryEach detected change is written to Full Enrich through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Full Enrich–Sharepoint connection.
Changes in Full Enrich or Sharepoint instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Full Enrich or Sharepoint data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Full Enrich or Sharepoint record.
Track your Full Enrich ⇄ Sharepoint sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Full Enrich and Sharepoint.
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 Full Enrich and Sharepoint 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 Full Enrich and Sharepoint 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.
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 377 integrations available for Full Enrich and Sharepoint.