About Custom Data in ConnectiveOne

Custom Data is your own tables inside the platform. You define structure (fields / columns), fill rows manually or via import — and processes can read, search, and store data. It replaces external sheets (Google Sheets, Excel) that need separate integration.

The v2 UI is a single workspace: Tables list on the left, records table in the center, Custom Data model editor for structure, Data import wizard for loading. Legacy tabs Create/Update, Groups, and Data are replaced by Menu → Custom Data navigation.

Typical uses:

• Store directory — bot shows addresses by city
• CSAT after dialogs — ratings in a table for reports
• Callback requests — operators see a list
• Categories, VIP lists, any automation directories

Core concepts

Table

A table is the main module entity (also called a “model”). Like a spreadsheet: fields are columns, rows are records.

Typical v2 flow:

1. Create table — landing /templates: Starters, From scratch, Ask AI, From file (Excel/CSV)
2. Define fields in the Custom Data model editor
3. Fill rows — manually, Data import, or from a process
4. Browse in Table / Board, Saved views, filters

Example: Stores table with city, address, phone, hours fields.

Fields and semantic types

Each field has a Type (text, number, email, Table relation, system User / Subject, etc.). Full list — Semantic field types reference.

Rows (records)

A row is one record (one store, one request). Edit in the grid, Card side panel, or via process.

Groups (two meanings)

• Group in Model metadata — table category in Custom Data models (no separate Groups tab).
• Record card groups — Accordion sections in the side panel; created on Field display.

Links between tables

Table relation stores another Custom Data record ID and shows its label (e.g. product category).

v2 workspace

Advanced features

Inline charts, Highlighting, Total row, Macros, advanced JSON — Advanced Custom Data cases, Advanced model options.

Large tables (hundreds of thousands of rows and more) stay available: if the chosen sort is not ready for a fast open, records are shown in a safe order with an explanation. Why this matters and how Custom Data compares — Compared to other approaches, How large tables work.

Client card extension

Prefer Client Fields (Settings) for new projects. Custom Data contact extension is for legacy setups.

Saving data from processes

1. Automatic — Save to Custom Data on input blocks. → Save data from a scenario
2. Process actions — custom_modules set/get/update. → Use the process tab

Benefits

• In-platform tables — structure, import, v2 workspace browsing
• Processes read and write — directories and requests in automation
• Import and Google Sheets — bulk load with preview

Tips

1. Plan fields before import — changing types later may trigger Review changes before save.
2. For search — Text, Email, List; for comments — Long text.
3. Add a unique field (email, code) for process lookup.
4. Try Starters or Ask AI for your first table.
5. Save frequent filters as a Saved view.

Custom Data and other data approaches

If you compare Custom Data with Google Sheets, automation-builder tables, or CRM — see About Custom Data compared to other approaches.

Related documents

• About Custom Data compared to other approaches
• How large tables work
• Integrator Hub
• Create a table
• Semantic field types reference
• Patterns and examples
• Advanced cases