Skip to content
9 platforms · typed · directional · audited

Connect everything. Speak one language.

Sumeru doesn't replace your tools — it connects them. Every system speaks to every other system through one runtime, one audit log, one identity layer. Every connection has explicit directionality: read, write, or both.

0
platforms · in + out
0 s
p95 ingest → action
0
retry attempts · DLQ after

4 ingest sources → 1 runtime → 4 outbound surfaces · animated paths show live event flow

By the data plane

Typed in. Typed out. Audited the whole way.

9
Platforms
2
Read-only
7
Read + write
P95 60s
Ingest → action
DLQ 4
Dead-letter after
365d
Audit retention
01 Connection inventory

Every integration is typed and directional.

Read-only, write-only, or bidirectional. Each connection has its own retry policy, its own throttle, its own audit row.

Shopify

read + write

Native deep integration. Storefront events, products, orders, customers, fulfillments. Mutations through cost-aware GraphQL throttle.

  • Webhook normalization · products / orders / fulfillments
  • Cost-aware GraphQL with 429 retry + backoff
  • Multi-storefront support under one tenant
  • Multi-currency + B2B native

Google Search Console

read

Daily ingest of queries, pages, AI Overview presence, Core Web Vitals. Drives the SEO Intelligence Engine + content decay detection.

  • Per-property quota tracking
  • AI Overview detection on searchAppearance
  • Core Web Vitals ingest

Google Ads

read + write

Campaign metrics ingest + bid + budget mutations. Token-bucket throttle per ad account so noisy accounts can't starve quiet ones.

  • MCC-aware (operating customer + login customer)
  • Conversions upload + audience sync
  • Per-keyword cost tracking + ROAS rollup

Google Analytics 4

read

Event-stream ingest for funnels, channel rollups, cohort retention. Serves the Analytics Intelligence Layer.

  • BigQuery + GA4 Data API
  • Channel attribution rollup
  • Cohort retention windows

Merchant Center

read + write

Product approval status snapshot daily. Disapproval-transition emit drives the mark_gmc_disapproval autoaction.

  • Daily approval-status snapshot
  • Disapproval-transition events
  • Per-product diagnostic surfacing

WhatsApp Cloud API

read + write

Outbound campaigns, transactional, cart recovery. Inbound webhook for delivery receipts + replies. Per-shop throttle on top of BullMQ-level limiter.

  • Outbound: campaigns / transactional / recovery
  • Inbound: delivery receipts + replies
  • Template management with approval-state cache

Meta Ads

read + write

Campaign metrics + audience sync + CAPI conversions upload. Per-account token bucket.

  • CAPI conversions upload
  • Audience sync (custom + lookalike)
  • Per-account rate-limit awareness

TikTok Ads

read + write

Campaign metrics + audience sync. Per-account token bucket. Conversions upload via Events API.

  • Events API conversions upload
  • Audience sync
  • Per-account token-bucket throttle

Public API + Webhooks

both

REST API for event ingest from any front-end. Outbound webhook subscriptions for autoaction.applied / autoaction.failed events.

  • OpenAPI spec for client generation
  • HMAC-SHA256 signed outbound payloads
  • Per-shop API keys with scope-minimization
  • Exponential backoff + dead-letter after 4 attempts
02 Connection primitives

Built for the failure cases, not the happy path.

Throttle, retry, dead-letter, idempotency, audit. Every connection inherits the same operational primitives.

Throttle
Token bucket per platform

Self-throttling helpers. Routes can't bypass. Cost-aware where the platform exposes cost (Shopify GraphQL).

Retry
Exponential backoff · 4 attempts

Failures retry with jitter. Permanent failures route to dead-letter queue with full payload + traceId.

Idempotency
Keyed inbound + outbound

Webhook duplicates rejected. Outbound mutations carry idempotency keys where the platform supports them.

Audit
365d default retention

Every cross-system action writes a plain-language audit row. Searchable by engine, action, severity, traceId.

Need a connection that isn't here?

The public REST API + outbound webhook system can connect Sumeru to anything. Common requests (Klaviyo, Segment, Mixpanel, Snowflake, dbt) are roadmap or already prototyped.