DatriseAI-first ETL

Square Spreadsheets

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

How Datrise loads Square into Spreadsheets

Datrise syncs Square's payments, orders, customers, catalog items, and locations 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

Square: Payments and commerce platform for retail and online sellers.

Spreadsheets: Business-friendly spreadsheet destination for collaborative analysis.

How Square entities map to Spreadsheets

Square entitySpreadsheets objectNotes
paymentssquare_paymentsid PK · custom fields → JSON-stringified cells for nested fields
orderssquare_ordersid PK · linked to square_payments
customerssquare_customersid PK · linked to square_payments
catalog itemssquare_catalog_itemsid PK · linked to square_payments

FAQ

How does Datrise handle Square'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 Square 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 Square 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.