Skip to content
Data warehouse ⇄ Business productivity

MotherDuck to Sysaid integration — real-time, two-way sync

Keep MotherDuck and Sysaid 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 MotherDuck and Sysaid

Get the data locked inside Sysaid into MotherDuck as live tables, and send results back where Sysaid can use them, without writing a pipeline.

Whatever Sysaid 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 Users, Assets, Configuration Items (CIs), Companies from Sysaid 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 Sysaid where the tool can use them.

Common use cases

  • 01 Sync Users, Groups, and Companies from an HRIS or identity provider so requester and agent records, departments, and managers stay current in SysAid.
  • 02 Mirror Assets and Configuration Items with an external CMDB or asset database so inventory and ticket linkage share one source of truth.
  • 03 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
  • 04 Sync modeled MotherDuck tables outward to operational tools for activation

Common sync patterns

Cross-tool reporting

Combine Sysaid's data with data from every other synced system to answer questions no single tool can.

Where Sysaid accepts updates: operational write-back

Segments, scores, or reference values computed in MotherDuck sync back onto records in Sysaid, putting analysis where the work happens.

History that outlives the tool

A continuously synced copy in MotherDuck preserves a queryable record even as data ages out of Sysaid or gets changed inside it.

What you can sync between MotherDuck and Sysaid

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.

MotherDuck objects Sysaid objects How this pairing syncs
Tables The main landing target for synced records and source for analysis. Service Requests Catalog and help-desk requests on the same /sr endpoint (type=request); written or read so fulfillment can be driven from another system. Tables is specific to MotherDuck and Service Requests to Sysaid — each maps to any object or custom field on the other side.
Views Modeled projections used as outbound sync sources. Problems Root-cause records that group related incidents; read and written to keep problem management aligned with an external ITSM or reporting store. Views is specific to MotherDuck and Problems to Sysaid — each maps to any object or custom field on the other side.
Database Shares Read-only copies of a database shared with other users or teams. Changes Change records (type=change) with approval and scheduling fields; synced two-way to drive CAB review and deployment workflows. Database Shares is specific to MotherDuck and Changes to Sysaid — each maps to any object or custom field on the other side.
Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. Users End users and admins on the /users endpoint; synced with an HRIS or identity source to keep requester and agent records current. Attached Local DuckDB Databases is specific to MotherDuck and Users to Sysaid — each maps to any object or custom field on the other side.
Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. Assets Hardware and software inventory; read out to a warehouse or written from a discovery or CMDB source of truth. Databases is specific to MotherDuck and Assets to Sysaid — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize synced tables. Configuration Items (CIs) CMDB entries and their relationships; synced with an external CMDB or asset database for one inventory view. Schemas is specific to MotherDuck and Configuration Items (CIs) to Sysaid — each maps to any object or custom field on the other side.

How changes propagate between MotherDuck and Sysaid

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.

MotherDuck Sysaid Interval-based propagation

DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

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

Sysaid MotherDuck Sub-second propagation

DetectionSysaid notifies Stacksync of record changes through webhook events. Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature.

DeliveryEach detected change is applied to MotherDuck as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
  • Sysaid: Requests are throttled per the X-RateLimit-Limit / -Remaining / -Reset headers; list calls are paginated with a limit parameter and each org is capped at 100 application keys.
What ships with MotherDuck ⇄ Sysaid

Connect MotherDuck and Sysaid for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in MotherDuck or Sysaid instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever MotherDuck or Sysaid 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 MotherDuck or Sysaid record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between MotherDuck and Sysaid.

How the MotherDuck and Sysaid connectors work

MotherDuck

Integration surface
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
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide

Sysaid

Integration surface
REST API (JSON)
Authentication
Client-credentials app keys: an application key (clientId/clientSecret) is created via /v1/application-keys, then exchanged at /v1/access-tokens for a bearer token (default 24h, up to 30 days); an x-sysaid-accountid header scopes the account. Legacy V0 uses session-cookie login.
Change detection
Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature; otherwise poll the /sr endpoint filtering on update_time.gte.
Capabilities
read · write · webhooks
Rate limits
Requests are throttled per the X-RateLimit-Limit / -Remaining / -Reset headers; list calls are paginated with a limit parameter and each org is capped at 100 application keys.
How it works

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

    Choose tables

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

MotherDuck and Sysaid 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 454 integrations available for MotherDuck and Sysaid.

Popular · 8 of 454
All MotherDuck integrations All Sysaid 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