1С:CRM to Redash Integration
AI-first ETL from 1С:CRM into Redash. Governed entities, incremental sync, typed landing tables.
How Datrise loads 1С:CRM into Redash
Datrise syncs 1С:CRM's counterparties, deals, interactions, orders, tasks, and business processes into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.
Ideal for lightweight, query-driven dashboards.
Endpoints
1С:CRM: CRM built on the 1C platform for sales and back-office.
Redash: Open-source SQL client for queries, visualizations, and dashboards.
How 1С:CRM entities map to Redash
| 1С:CRM entity | Redash object | Notes |
|---|---|---|
| counterparties | 1c_crm_counterparties | id PK · custom fields → flattened columns for query results |
| deals | 1c_crm_deals | id PK · linked to 1c_crm_counterparties |
| interactions | 1c_crm_interactions | id PK · linked to 1c_crm_counterparties |
| orders | 1c_crm_orders | id PK · linked to 1c_crm_counterparties |
FAQ
How does Datrise handle 1С:CRM's custom fields in Redash?
Flexible values are stored as flattened columns for query results, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Redash types.
How does the 1С:CRM to Redash sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for 1С:CRM
Early access
Connect 1С:CRM to Redash 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.