DatriseAI-first ETL

Smaily to Spreadsheets Integration

AI-first ETL from Smaily into Spreadsheets. Governed entities, incremental sync, typed landing tables.

How Datrise loads Smaily into Spreadsheets

Datrise syncs Smaily's subscribers, campaigns, lists, autoresponders, email events, and segments into Spreadsheets as a tab per source entity. Flexible or custom fields land in JSON-stringified cells for nested fields, and timestamps such as created, updated, and status changes are typed as ISO-8601 text or serial date cells.

Sync is incremental: Datrise uses refreshes the tab's rows each run, preserving header order, so re-runs update only what changed. Sheets caps out around the low millions of cells, so Datrise lands a curated column set rather than every raw field.

Ideal for lightweight, shareable reporting for non-technical teams.

Endpoints

Smaily: Email and SMS campaigns with subscriber segments.

Spreadsheets: Business-friendly spreadsheet destination for collaborative analysis.

How Smaily entities map to Spreadsheets

Smaily entitySpreadsheets objectNotes
subscriberssmaily_subscribersid PK · custom fields → JSON-stringified cells for nested fields
campaignssmaily_campaignsid PK · linked to smaily_subscribers
listssmaily_listsid PK · linked to smaily_subscribers
autoresponderssmaily_autorespondersid PK · linked to smaily_subscribers

FAQ

How does Datrise handle Smaily's custom fields in Spreadsheets?

Flexible values are stored as JSON-stringified cells for nested fields, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Spreadsheets types.

How does the Smaily to Spreadsheets sync stay up to date?

It runs incrementally — Datrise uses refreshes the tab's rows each run, preserving header order.

Related pipelines

Early access

Connect Smaily to Spreadsheets the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.