Skip to main content

Agent Serve · Tables

Working data, right where the work is.

Keep account lists, review queues and case records in typed tables. Add a workflow column and watch it fill in, row by row.

Agent Serve Tables is the built-in database of Agent Serve, the AI workspace where teams build, deploy, and manage AI agents. Tables hold typed records that agents, workflows and dashboards use, with workflow columns that run on every row and access rules that limit rows and columns by person, team or role.

How it works

From a spreadsheet to a working queue.

Agent Serve Tables turns a pasted sheet or an imported file into records that agents, workflows and people keep current together.

  1. 1

    Bring the data in

    Paste cells from Excel or Google Sheets, or import a CSV, TSV or Excel file and map its columns.

  2. 2

    Give every column a type

    Text, number, date, boolean, select, currency and JSON columns keep each value meaning one thing.

  3. 3

    Run a workflow per row

    A workflow column runs a workflow on each row and writes its outputs back into the table.

  4. 4

    Use it everywhere

    Agents, Chat, dashboards and monitors read the same rows, under the same access rules.

Capabilities

A table your agents can actually use.

Typed columns

Agent Serve Tables columns are text, number, boolean, date, select, currency or JSON, and can be required or unique.

Account · Owner · Renewal date · ARR (USD)

Workflow columns

Agent Serve runs a workflow on each row, with inputs from the row and outputs written to columns you choose.

Run cell · Run empty or failed cells

Enrichments

Agent Serve enrichments fill work email, phone, LinkedIn profile, company domain and company info, trying several data providers in turn.

Company info · matched on the second provider

Saved views

An Agent Serve view saves its filters, sort, column order, widths, pins and hidden columns, and one view is the default.

All · Open disputes · Past deadline

Live together

Agent Serve shows who else is in the table and what they have selected, so two people never edit blind.

Presence avatars · shared selections

Ask about this table

One click sends the table to Agent Serve Chat, which can query rows, add columns and build views for you.

“Which disputes are past 30 days?”

Access

Everyone sees only what they should.

Row limits narrow which rows a person or team sees, and restricted columns hide sensitive fields from everyone you do not name.

  • Rules for users, teams or roles
  • Applied to row reads, table reads and exports
  • Workspace admins keep full access
  • Admins can deny inserts, updates, deletes or schema changes

Examples

Queues financial teams run on Tables.

Three tables banks and insurers keep in Agent Serve, each one a queue that used to live in a shared spreadsheet.

Cards · Disputes

Chargeback deadline queue

An Agent Serve table holds every open dispute with its network deadline, and a workflow column drafts the evidence summary for each one.

  1. Dispute row added
  2. Table Trigger fires
  3. Evidence summary drafted
  4. Analyst reviews
Compliance · KYC

Periodic review backlog

Customers due for KYC refresh sit in an Agent Serve table; a workflow checks each file and marks what is missing.

  1. Due date reached
  2. Documents checked
  3. Gaps listed
  4. Case assigned
Insurance · Claims

Claims intake register

New claims land as rows in an Agent Serve table, and a workflow column classifies severity before a handler picks them up.

  1. Claim received
  2. Row inserted
  3. Severity classified
  4. Handler assigned

Examples show what teams can build in Agent Serve. They describe patterns, not named customer deployments.

Under the hood

Agent Serve Tables, in detail.

Agent Serve Tables, in detail.
Column typesText, Number, Boolean, Date, Select (single or multi), Currency (ISO 4217) and JSON.
ColumnsUp to 1,000 per table, each optionally required or unique.
ImportPaste from Excel or Google Sheets, or import .csv, .tsv, .xlsx and .xls files, appending or replacing rows.
ExportExport CSV from the toolbar. Large tables export as a background job.
FiltersEquals, contains, starts with, greater or less than, in a list, is empty and more, combined with and / or.
Workflow blockThe Table block inserts, upserts, updates and deletes rows by ID or by filter, gets a row by ID and reads the schema.
Table TriggerStarts a workflow on Row Inserted, Row Updated or Row Deleted, optionally for chosen columns.
APIA REST API with API keys covers tables, rows, columns, views, imports and exports.

Governance

Rules that travel with the data.

Agent Serve enforces table access wherever rows are read, so a person, an agent and an export all see the same slice.

Security and governance
  • Row limits and restricted columns

    Agent Serve limits a person or team to the rows they own and hides restricted columns from everyone not listed.

  • Table Security

    Agent Serve admins can deny inserting, updating or deleting rows, or changing the schema, on every surface at once.

  • Recorded and restorable

    Agent Serve records table creation, changes, deletion, restore and export in the audit log, and deleted tables can be restored.

  • Row-level access

    Row-level policies narrow what each person sees in tables, dashboards, exports and scheduled reports.

  • Roles and permission groups

    Admin, write and read roles per workspace, plus permission groups that limit which models, blocks and integrations a team can use.

  • Self-hosting

    Run Agent Serve in your own cloud or data centre, next to the systems it reads.

  • GDPR ready

    Retention from one day to five years, deletion and access controls support GDPR obligations. Ready means the controls are in place, not a certification.

Before and after

One table instead of five spreadsheets.

One table instead of five spreadsheets.
WorkBeforeWith Agent Serve
Where the queue livesBeforeA shared spreadsheet, copied into email and renamed “final_v3”.With Agent ServeOne Agent Serve table with typed columns and saved views for each team.
Filling in the blanksBeforeSomeone works down the rows by hand, one lookup at a time.With Agent ServeA workflow column runs on every row and fills the result in.
Who sees whatBeforeSeparate copies for each team, already out of date.With Agent ServeRow limits and restricted columns on the one table.
Acting on a changeBeforeSomeone notices a new row the next morning.With Agent ServeA Table Trigger starts a workflow the moment a row changes.

Works with

Tables feed the rest of Agent Serve.

Further reading

Solutions built on Agent Serve Tables.

Questions

About Tables

Can agents use workspace tables?

Yes. Agent Serve tables hold structured records that agents, workflows and Chat can read and write, subject to the access of the person or workflow using them.

What is a workflow column?

A workflow column runs an Agent Serve workflow on each row, using values from the row as inputs and writing the outputs to the columns you choose. You can run one cell, the empty or failed cells, or the whole column.

How do I get data into a table?

Paste cells from Excel or Google Sheets, import a CSV, TSV or Excel file, or insert rows from a workflow, Chat or the Agent Serve API.

Can I limit which rows each person sees?

Yes. Agent Serve row limits narrow the rows a person or team sees, and restricted columns hide fields from anyone not listed. The limits also apply to exports.

Can a table start a workflow?

Yes. The Agent Serve Table Trigger starts a workflow when a row is inserted, updated or deleted, and can watch only the columns you choose.

Last updated

Enterprise access

Put AI agents to work across your team

Agent Serve is available to teams by invitation. Tell us what you want to build and we will set up your workspace with you.