AAtlasLoopOSGTM operating system
Betaatlaspipe

Bring governed CSV and webhook data into canonical GTM records.

Create tenant-scoped data sources, upload UTF-8 CSV files, preview detected columns and types, review every mapping, validate rows, import normalized GTM records, and inspect synchronization evidence. Tokenized webhook intake is implemented; Google Ads, Meta Ads, GA4, HubSpot, and Pipedrive remain explicit non-executable placeholders.

Open authenticated workspace Read step-by-step guideProduct catalog

Runtime availability depends on the canonical product status, organization entitlement, workspace permissions, deployment configuration, and any provider-specific authorization required by the workflow.

Who it is for

  • Operators who need a controlled data-ingestion path with preview, mapping, validation, deduplication, canonical account/contact records, and synchronization evidence.

Codebase contract

  • Application route: /products/atlaspipe
  • Required permissions: atlaspipe.access

How the current workflow works

  1. 1Select an entitled workspace and create or choose a tenant-scoped AtlasData source.
  2. 2Upload a UTF-8 CSV file and wait for the bounded durable preview.
  3. 3Review detected columns, inferred types, and the staged upload identifier before importing anything.
  4. 4Map source columns to the supported canonical account and contact fields.
  5. 5Review validation and deduplication behavior, then confirm the staged upload once.
  6. 6Inspect imported, failed, and duplicate counts plus row-level synchronization evidence.
  7. 7Use the source, mapping, sync-log, and data-health views to correct issues and verify the normalized result.
  8. 8For machine intake, create and inspect a tokenized webhook endpoint only inside an authorized workspace.

Current codebase capabilities

  • Tenant-scoped data-source management for CSV and tokenized webhook intake.
  • Durable CSV preview with detected columns and types.
  • Explicit mapping review before one-time confirmation.
  • Validation, deduplication, canonical account/contact ingestion, and provenance.
  • Synchronization logs and data-health views for the selected workspace.

Current boundaries

  • The stable internal key and API namespace remain atlaspipe for compatibility.
  • Google Ads, Meta Ads, GA4, HubSpot, and Pipedrive are explicit non-executable placeholders in the current Beta.
  • A named connector in the UI does not confirm that the connector is enabled.
  • Limited Beta status does not represent a production service-level commitment.

Manifest capabilities and permissions

These identifiers are read directly from the canonical frontend product manifest. They describe access boundaries and capability names; they do not by themselves prove provider configuration or runtime availability.

Capabilities

atlaspipe.accessatlaspipe.sources.manageatlaspipe.csv.importatlaspipe.webhooks.manageatlaspipe.mappings.manageatlaspipe.logs.viewatlaspipe.health.viewatlaspipe.sync.runatlaspipe.api.validate_license

Required permissions

atlaspipe.access

What to verify after using it

  • The preview and confirmed import refer to the same staged upload.
  • Imported contacts/accounts preserve source and upload provenance without creating unexpected duplicates.
  • Sync logs show imported, rejected, and duplicate counts that match the confirmed operation.