Skip to content
Database ⇄ Accounting and finance

Google Cloud SQL to Pigment integration — real-time, two-way sync

Keep Google Cloud SQL and Pigment 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 Google Cloud SQL and Pigment

Work with Pigment's financial data straight from Google Cloud SQL: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Users and permissions, Applications, Metrics, Dimension lists from Pigment into Schemas, Tables, Rows, Views in Google Cloud SQL and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Google Cloud SQL, and rows your code writes or updates flow back into Pigment with validation, so the finance system stays the system of record.

Common use cases

  • 01 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • 02 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • 03 Migrate from a self-managed database by syncing Cloud SQL and the legacy system during cutover.
  • 04 Keep an internal admin application backed by Cloud SQL consistent with an ERP or billing system.

Common sync patterns

Query finance data like any other data

Customers, invoices, and payments from Pigment live in Google Cloud SQL as regular tables or collections your team can join, index, and query.

Internal tools without API plumbing

Build dashboards and back-office tools directly on Google Cloud SQL; Stacksync handles the API calls, rate limits, and retries against Pigment.

Write back safely

Updates written to the synced tables in Google Cloud SQL propagate into Pigment, so automations can create or correct finance records without custom integration code.

What you can sync between Google Cloud SQL and Pigment

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.

Google Cloud SQL objects Pigment objects How this pairing syncs
Tables Mapped directly to sync targets; schema changes can be propagated. Tables Row-based transactional data loaded into models from source systems Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Schemas Namespace tables in PostgreSQL and SQL Server instances. Metrics Multidimensional values holding plans and actuals; the main target for inbound data Schemas is specific to Google Cloud SQL and Metrics to Pigment — each maps to any object or custom field on the other side.
Rows Read and written by primary key during each sync cycle. Dimension lists Master data like accounts, products, or employees that metrics are sliced by Rows is specific to Google Cloud SQL and Dimension lists to Pigment — each maps to any object or custom field on the other side.
Views Read-only sources for shaping data before syncing it out. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Views is specific to Google Cloud SQL and Scenarios to Pigment — each maps to any object or custom field on the other side.
Transaction logs MySQL binlog or PostgreSQL WAL, the source for log-based change capture. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Transaction logs is specific to Google Cloud SQL and Data imports to Pigment — each maps to any object or custom field on the other side.
Instances The managed MySQL, PostgreSQL, or SQL Server server a sync connects to. Users and permissions Access controls governing which model areas a sync can touch Instances is specific to Google Cloud SQL and Users and permissions to Pigment — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud SQL and Pigment

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.

Google Cloud SQL Pigment Sub-second propagation

DetectionChanges in Google Cloud SQL are captured at the source via change data capture — no polling loop against its API. Engine-dependent log-based CDC: MySQL binlog, PostgreSQL logical replication, SQL Server change tracking.

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

Pigment Google Cloud SQL Interval-based propagation

DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.

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

Rate-limit considerations

  • Google Cloud SQL: Constrained by instance size and connection limits rather than API quotas.
  • Pigment: Subject to the platform's API rate limits.
What ships with Google Cloud SQL ⇄ Pigment

Connect Google Cloud SQL and Pigment for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud SQL–Pigment connection.

Real-time

Two-way sync

Changes in Google Cloud SQL or Pigment instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Google Cloud SQL or Pigment 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 Google Cloud SQL or Pigment record.

Observability

Monitoring

Track your Google Cloud SQL ⇄ Pigment sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Cloud SQL and Pigment.

How the Google Cloud SQL and Pigment connectors work

Google Cloud SQL

Integration surface
Native SQL wire protocols (MySQL, PostgreSQL, SQL Server) plus a REST admin API for instance management
Authentication
Database credentials; IAM database authentication is available for MySQL and PostgreSQL
Change detection
Engine-dependent log-based CDC: MySQL binlog, PostgreSQL logical replication, SQL Server change tracking; polling as a fallback
Capabilities
read · write · CDC
Rate limits
Constrained by instance size and connection limits rather than API quotas.

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

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

    Choose tables

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

Google Cloud SQL and Pigment 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 342 integrations available for Google Cloud SQL and Pigment.

Popular · 5 of 342
All Google Cloud SQL integrations All Pigment 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