Skip to content
Database ⇄ Business productivity

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

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

Mirror Sysaid's data into Citus so your own code can read and write it like any other table, with changes flowing both ways in seconds.

Engineers integrate with tools like Sysaid through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Citus.

Stacksync mirrors Custom Fields, Incidents, Service Requests, Problems from Sysaid into Local tables, Schemas, Views, Sequences in Citus and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Sysaid, so the tool and the database never disagree.

Common use cases

  • 01 Two-way sync Incidents and Service Requests with a Postgres database so on-call and internal apps read and update tickets in SQL while agents keep working in SysAid.
  • 02 Create SysAid Incidents from monitoring or error-tracking alerts, then write status and resolution back so both systems stay aligned.
  • 03 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
  • 04 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.

Common sync patterns

Read Sysaid with a query

Records from Sysaid are ordinary rows in Citus; join them, index them, and use them in application logic without touching the vendor API.

Automate Sysaid from your codebase

Write to the synced tables in Citus and Stacksync propagates the change into Sysaid, replacing custom integration code.

React to changes as they happen

Updates in Sysaid arrive as row changes in Citus, so triggers, jobs, and services can respond in near real time.

What you can sync between Citus 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.

Citus objects Sysaid objects How this pairing syncs
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. 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. Local tables is specific to Citus and Service Requests to Sysaid — each maps to any object or custom field on the other side.
Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Problems Root-cause records that group related incidents; read and written to keep problem management aligned with an external ITSM or reporting store. Schemas is specific to Citus and Problems to Sysaid — each maps to any object or custom field on the other side.
Views Curated projections over distributed data, often used as read-only sync sources. Changes Change records (type=change) with approval and scheduling fields; synced two-way to drive CAB review and deployment workflows. Views is specific to Citus and Changes to Sysaid — each maps to any object or custom field on the other side.
Sequences Key generators that matter when external writes must not collide with application inserts. Users End users and admins on the /users endpoint; synced with an HRIS or identity source to keep requester and agent records current. Sequences is specific to Citus and Users to Sysaid — each maps to any object or custom field on the other side.
Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Assets Hardware and software inventory; read out to a warehouse or written from a discovery or CMDB source of truth. Distributed tables is specific to Citus and Assets to Sysaid — each maps to any object or custom field on the other side.
Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Configuration Items (CIs) CMDB entries and their relationships; synced with an external CMDB or asset database for one inventory view. Reference tables is specific to Citus and Configuration Items (CIs) to Sysaid — each maps to any object or custom field on the other side.

How changes propagate between Citus 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.

Citus Sysaid Sub-second propagation

DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.

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

Sysaid Citus 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 Citus as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • 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 Citus ⇄ Sysaid

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Citus and Sysaid connectors work

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC

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 Citus 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 Citus 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
    Citus connected
    Sysaid connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Citus 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 437 integrations available for Citus and Sysaid.

Popular · 7 of 437
All Citus 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