Real-time
Two-way sync
Changes in Google Cloud Platform or Pigment instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Accounting and finance
Google Cloud Platform to Pigment integration — real-time, two-way sync
Keep Google Cloud Platform 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 Platform and Pigment
Land the financial records from Pigment in Google Cloud Platform continuously, and write results back, without building or maintaining a pipeline.
Finance data belongs in the warehouse: revenue, invoices, payments, and customers joined with everything else the business measures. Getting it there usually means an extraction pipeline that breaks quietly and delivers yesterday's numbers.
Stacksync syncs Data imports, Users and permissions, Applications, Metrics from Pigment into tables in Google Cloud Platform in real time, and the connection works in both directions: values computed in Google Cloud Platform can be written back to fields in Pigment where you want them operational. Schema changes are handled, API limits are managed, and the sync is something you configure rather than code you maintain.
Common use cases
- 01 Sync headcount and compensation data from an HRIS into workforce planning models.
- 02 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- 03 Publish change events to Pub/Sub so downstream services react to record updates as they happen.
Common sync patterns
Queryable history for audit and reconciliation
A continuously synced copy in Google Cloud Platform gives you a durable, queryable record of financial data for month-end and audit questions.
Finance analytics without ETL
Invoices, payments, and customer records from Pigment arrive in Google Cloud Platform as queryable tables, current within seconds instead of a day behind.
Revenue joined with everything else
Analysts combine Pigment's financial records with product, marketing, or operational data already in Google Cloud Platform for reporting the finance system cannot do alone.
What you can sync between Google Cloud Platform 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 Platform objects | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Cloud SQL databases Managed Postgres, MySQL, and SQL Server instances synced like ordinary relational databases. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Cloud SQL databases is specific to Google Cloud Platform and Scenarios to Pigment — each maps to any object or custom field on the other side. | |
| Cloud Storage objects Staging area for file-based bulk loads into BigQuery and other services. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Cloud Storage objects is specific to Google Cloud Platform and Data imports to Pigment — each maps to any object or custom field on the other side. | |
| Pub/Sub topics Event streams used to move change events between systems in near real time. | Users and permissions Access controls governing which model areas a sync can touch | Pub/Sub topics is specific to Google Cloud Platform and Users and permissions to Pigment — each maps to any object or custom field on the other side. | |
| Firestore documents Document data read and written through the Firestore API for app-facing syncs. | Applications Planning models organized by domain such as finance, sales, or workforce | Firestore documents is specific to Google Cloud Platform and Applications to Pigment — each maps to any object or custom field on the other side. | |
| Spanner tables Strongly consistent relational tables accessed via SQL for transactional workloads. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Spanner tables is specific to Google Cloud Platform and Metrics to Pigment — each maps to any object or custom field on the other side. | |
| BigQuery datasets Namespaces that group tables; syncs target tables within a dataset. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | BigQuery datasets is specific to Google Cloud Platform and Dimension lists to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Google Cloud Platform 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 Platform Pigment Sub-second propagation
DetectionGoogle Cloud Platform pushes changes as they happen — webhook events backed by change data capture. Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery.
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Google Cloud Platform 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 Platform as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Google Cloud Platform: Quotas are set per service and per project; BigQuery, Pub/Sub, and Cloud SQL each enforce their own limits.
- Pigment: Subject to the platform's API rate limits.
What ships with Google Cloud Platform ⇄ Pigment
Connect Google Cloud Platform and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Platform–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Google Cloud Platform 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 Platform or Pigment record.
Observability
Monitoring
Track your Google Cloud Platform ⇄ 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 Platform and Pigment.
How the Google Cloud Platform and Pigment connectors work
Google Cloud Platform
- Integration surface
- Per-service REST and gRPC APIs; BigQuery speaks SQL and Cloud SQL exposes standard database wire protocols
- Authentication
- IAM service accounts with OAuth 2.0 tokens
- Change detection
- Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery tables
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- Quotas are set per service and per project; BigQuery, Pub/Sub, and Cloud SQL each enforce their own limits
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 Platform 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.
- 01
Connect your apps
Authenticate Google Cloud Platform 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.
Google Cloud Platform
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Google Cloud Platform 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.
objects · Google Cloud Platform ⇄ PigmentCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Google Cloud Platform PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Google Cloud Platform and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Google Cloud Platform and Pigment: authenticate both systems, choose the objects to sync (such as Google Cloud Platform's Cloud SQL databases and Cloud Storage objects), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Pigment: Pigment's model is multidimensional: metrics are sliced by dimension lists, so inbound records must map to those dimensions rather than flat columns. Google Cloud Platform: Authentication is uniform across services through IAM service accounts, so one credential model covers BigQuery, Cloud SQL, Cloud Storage, and Pub/Sub. Stacksync's field mapping accounts for these differences between Google Cloud Platform and Pigment 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 Google Cloud Platform and Pigment records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Google Cloud Platform and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Google Cloud Platform–Pigment integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Google Cloud Platform and Pigment. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Google Cloud Platform: Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery tables. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 444 integrations available for Google Cloud Platform and Pigment.
Popular · 4 of 444
-
Google Cloud Platform ⇄ Adyen -
Google Cloud Platform ⇄ Logisense -
Google Cloud Platform ⇄ Bill -
Google Cloud Platform ⇄ Braintree
No integrations match .
