> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/workflow-builder/nodes/built-in-resources/diaflow-tables.md).
# Diaflow Tables
Diaflow Tables help you store, find, and update structured data inside your workspace, so your workflows can use that data at each node.
Use them when your automation needs a reliable place to read from, write to, and keep business data up to date.
## When to use Diaflow Tables
* When you want to store customers, orders, tickets, leads, tasks, or internal operations data.
* When a workflow needs to look up information before making a decision.
* When a workflow needs to save new data after a form, approval, or AI node.
* When a workflow needs to update status, results, or existing records.
* When you want table data to become part of your automation logic.
## What you can do with Diaflow Tables
### Find and read records
Use Diaflow Tables to:
* View one specific record.
* Find records that match a condition.
* List many records at once.
* Count how many records are in a table.
### Add new records
Add one new row or many rows in a single workflow node.
This is useful when a workflow collects new information and needs to save it right away.
### Update existing records
Change values that already exist in a table.
For example, you can update a status, assign an owner, or save a processing result.
### Delete records
Remove records when they are no longer needed.
This helps keep operational data clean and current.
### Create or adjust table structure
Diaflow Tables can also help you manage the table itself.
At a high level, you can:
* Create a new table.
* Review the current table structure.
* Add, edit, or remove columns.
* Clear all data from a table when needed.
### Use table changes in automation
Table updates can drive the next node in a workflow.
For example, when a record is added or updated, your workflow can continue with follow-up actions such as notifications, approvals, or enrichment.
## Simple mental model
You can think of Diaflow Tables as a spreadsheet that connects directly to your workflow.
Your workflow can read data from the table, send that data into logic or AI nodes, and then write the result back into the same table.
## Common examples
* Count how many leads are in a table.
* Find a customer by email before sending a message.
* Add a new support ticket after a form submission.
* Update order status after an approval node.
* Create a new row when AI extracts information from a document.
## Basic configuration overview
* **Action**: Choose what you want Diaflow Tables to do, such as find, add, update, delete, list, or count.
* **Table**: Choose the table your workflow should use.
* **Input / Mapping**: Provide the data, conditions, or field mapping needed for that action.
* **Optional settings**: Some actions support extra options, such as caching or filtering.
For detailed setup of each action, see the action-specific pages.
## More than the legacy version
Older flows may still use the earlier action set.
Diaflow Tables now support much more than the original query, add, and update pattern. They now cover read, search, list, count, add, update, delete, upsert and basic table structure management in one place.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.diaflow.io/workflow-builder/nodes/built-in-resources/diaflow-tables.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.