Skip to content
DataSquaresDocs

Activations (reverse-ETL)

While standard pipelines extract data into DataSquares, Activations perform governed reverse-ETL: sending curated business metrics and managed datasets out to external SaaS platforms, CRM systems, and webhook endpoints on automated schedules.

Manage activations under Pipelines → Activations.

What you can activate

Section titled “What you can activate”
Source Kind Description Query Execution & Scope
Metric A governed metric (current scalar value or timeseries) Evaluated through the semantic engine under a pinned run-as identity
Dataset A managed dataset in the DataSquares warehouse Read via tenant-scoped database drivers

Security & data governance

Section titled “Security & data governance”

Activations are strictly governed to ensure external delivery never bypasses access controls:

  • Pinned run-as identity — Metric activations execute with the permissions of the configured user. Row-Level Security (RLS) policies apply identically to dashboard views.
  • Masking enforcement — Masked or sensitive columns are refused outright on external activation paths, preventing accidental export of PII to third-party receivers regardless of user role.
  • Destination redirect protection — Target webhook URLs are strictly validated before each transmission; HTTP 3xx redirects are refused to prevent destination hijack.

Creating an activation

Section titled “Creating an activation”
  1. Navigate to Pipelines → Activations and click New activation.
  2. Enter an activation name.
  3. Choose the Source Type:
    • Metric: Pick a governed metric and select scalar or timeseries format.
    • Dataset: Pick a managed warehouse dataset.
  4. Provide the destination Webhook URL and optional custom HTTP headers.
  5. Set the Schedule (Hourly, Daily, Weekly, or manual trigger).
  6. Click Save activation.

Delivery protocol & signature verification

Section titled “Delivery protocol & signature verification”

Rows are transmitted as batched JSON payloads via HTTP POST requests.

Request headers

Section titled “Request headers”
POST https://api.yourservice.com/v1/ingest
Content-Type: application/json
X-DataSquares-Timestamp: 1724587200
X-DataSquares-Delivery-Id: 550e8400-e29b-41d4-a716-446655440000:0
X-DataSquares-Signature: f9b2c34...

Signature verification

Section titled “Signature verification”

Every delivery request includes an X-DataSquares-Signature header computed as the HMAC-SHA256 hex digest of "{timestamp}.{deliveryId}.{payload}" using your workspace secret.

Idempotency & rate limiting

Section titled “Idempotency & rate limiting”
  • Stable delivery IDs — The X-DataSquares-Delivery-Id format (<activationRunId>:<batchIndex>) is stable across retries, enabling idempotent ingestion on the receiving server.
  • Retry-After compliance — If the destination endpoint returns HTTP 429 or HTTP 503 with a Retry-After header, DataSquares pauses delivery without exhausting retry attempts.

Delivery history & monitoring

Section titled “Delivery history & monitoring”

Click any activation row in the Activations table to expand its Delivery history:

  • Shows the last 20 execution runs with start times, completion duration, total rows delivered, and status badges (succeeded / failed).
  • Displays detailed error diagnostics if the remote endpoint returns non-2xx status codes.
  • Use Run now to trigger an immediate out-of-band delivery to test endpoint connectivity.
Section titled “Related”
© 2026 DataSquares