Tables
Tables hold structured records — the lists a marketing team keeps in a spreadsheet and then loses track of. A prospect list, client accounts, a content calendar, competitor tracking, campaign naming decisions. They live in Adlyse so your agents and workflows can read and write them.
In one line
If it’s a list of things with the same fields, it’s a table. If it’s a document, it belongs in Files.
Creating one#
Go to Knowledge → Tables → New table. Give it a name, pick its type — Accounts, Contacts, Deals, or Custom — and define your columns.
Columns can be text, number, date, date & time, checkbox, single or multi select, email, URL, a link to a record in another table, or a person from your organization. Star a table to pin it to the top of your list.
Enrichment: filling a column with AI#
This is what makes a table more than a spreadsheet. Any column can be enriched by an agent or workflow: you map its inputs to your existing columns and its output back into the column you’re filling, then run it across the rows.
You control what gets skipped, which matters when you re-run:
- Skip if any output column has a value — the usual choice.
- Skip if all output columns have values.
- Skip if previously enriched — never touch a row that already succeeded.
- Never skip — re-run everything.
The pattern this unlocks: paste in 200 competitor URLs, add an empty “positioning” column, point an enrichment at it, and come back to 200 filled cells.
Tables in workflows#
A workflow can use a table at either end. The Data enrichment trigger fires when a row is added or changed, so new rows get processed as they arrive. And any workflow can read rows, work through them with a List Operator node, and write results back.
Agents and tables#
An agent with the Data tables capability can query rows, create tables and columns, and add, update, or delete rows.
Your synced ad data stays off-limits
This capability covers the tables you create. Adlyse’s own record of your synced platform performance isn’t writable through it — an agent can’t rewrite your spend history.
Common flows#
- Enrich a prospect list. Upload the rows, add the columns you wish you had, let an agent fill them.
- Track competitors properly. One row per rival, with columns for positioning and current offer, refreshed on a schedule.
- Keep a decision log your team maintains. Naming conventions, budget rules, what you tried and why — structured, so it stays searchable.
Documents and standing instructions, for anything that isn’t a list.
WorkflowsTrigger on new rows, or process a whole table item by item.
Tool groupsGive an agent the Data tables capability.
Brand profileThe other half of what Adlyse works from.
Work with tables directly via list_tables, create_table, query_table_rows, and update_table_rows.