Two-way sync
Changes in Full Enrich or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Keep Full Enrich and MotherDuck 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 Full Enrich 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 Contacts, Enrichment results, Emails, Phone numbers from Full Enrich into tables in MotherDuck continuously, handling schema, rate limits, and retries. Because the sync is bi-directional, results computed in MotherDuck can also be written back into fields in Full Enrich where the tool can use them.
Segments, scores, or reference values computed in MotherDuck sync back onto records in Full Enrich, putting analysis where the work happens.
A continuously synced copy in MotherDuck preserves a queryable record even as data ages out of Full Enrich or gets changed inside it.
Records and events from Full Enrich land in MotherDuck as queryable tables, current within seconds and ready to join with the rest of the warehouse.
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 | MotherDuck objects | |
|---|---|---|
| Emails Returned addresses with verification status, written back to the CRM or database. | Database Shares Read-only copies of a database shared with other users or teams. | |
| Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | |
| Credits Account balance consumed on successful finds; monitored to pace sync jobs. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | |
| Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. | Schemas Namespaces within a database used to organize synced tables. | |
| Contacts The person inputs (name plus company or domain) sent for enrichment. | Tables The main landing target for synced records and source for analysis. | |
| Enrichment results Completed records fetched by request ID or delivered via webhook. | Views Modeled projections used as outbound sync sources. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Full Enrich–MotherDuck connection.
Changes in Full Enrich or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Full Enrich or MotherDuck 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 MotherDuck record.
Track your Full Enrich ⇄ MotherDuck sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Full Enrich and MotherDuck.
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 MotherDuck 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 MotherDuck 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 Full Enrich and MotherDuck: authenticate both systems, choose the objects to sync (such as Full Enrich's Emails and Phone numbers), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Full Enrich and MotherDuck: Where Full Enrich accepts updates: operational write-back; History that outlives the tool; Analytics on Full Enrich's data. Segments, scores, or reference values computed in MotherDuck sync back onto records in Full Enrich, putting analysis where the work happens.
Full Enrich: REST API with asynchronous bulk enrichment endpoints. Authentication: API key (Bearer token). MotherDuck: SQL through DuckDB clients and drivers using a MotherDuck (md:) connection. Authentication: Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults. Stacksync manages authentication, retries, and rate limits on both sides.
Full Enrich: Credits are consumed on successful finds, so integration logic should distinguish found, not-found, and in-progress outcomes when writing back. MotherDuck: Databases can be shared with other users as read-only shares, separating producers from consumers. Stacksync's field mapping accounts for these differences between Full Enrich and MotherDuck without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Full Enrich and MotherDuck records are not retained after a sync operation.
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 Full Enrich and MotherDuck.