Where data lands · Autessa Synthetic Data
Seed an existing table
Autessa Synthetic Data seeds an existing database table. Pick the table, describe the data, and Autessa generates rows that fit the table’s columns, ranges and allowed values, then writes them with your own table permissions.
The problem
An empty table makes a poor demo and a weak test
Apps, dashboards and agents built on a table only show their value once the table has realistic data. Typing rows by hand is slow, and importing a spreadsheet means building the spreadsheet first.
What you get
- Pick from tables you own, tables shared with the company, and tables shared with you.
- The table’s schema is shown before you start: every column, with its type.
- Media columns are flagged "not generatable" and left empty.
- Rows respect the table’s required columns, number ranges, text lengths and allowed values.
- Rows are written as you, with your access to the table.
- Generated rows count against your database storage limit; if it is reached, the job ends partially completed.
- Inserted rows do not fire the table’s triggers.
How it works
How does seed an existing table work?
Choose Existing table
In "1. Target", pick Existing table and select the table from the list.
Check the schema
The schema panel lists every column and type, and marks media columns that will be left empty.
Describe and size it
Name the dataset, describe the data and choose 1 to 5,000 rows.
Review or write directly
Review first stages rows for approval; Write directly inserts each batch as it is ready.
Open the table
When the job completes, "View in table" opens the filled table.
Every option
Existing table options
| Option | What it does |
|---|---|
| Table | Required. Any table you can access: owned, shared with the company, or shared with you. |
| Columns | Taken from the table. No schema editing needed. |
| Media columns | File, image, audio and video columns are flagged and left empty. |
| Write mode | Review first or Write directly. |
| Triggers | Inserted rows do not fire table triggers, so seeding never sets off your automations. |
| Storage | Rows count against your database storage limit. |
Example
Seed a table from the CLI
Replace the ids with your own.
Permissions
Who can do what?
| Who | Can |
|---|---|
| People in your company | Create datasets, see the company list of jobs, open any job and review, approve, append, cancel or discard it. |
| Table permissions | Rows written into a table are written as the person who started the job, with that person’s access to the table. |
| API keys | Cannot target tables. Use a dataset file or quick generate with an API key. |
Connected
How seed an existing table connects to the rest of Autessa
FAQ
Questions about seed an existing table
Will seeding a table run its triggers or automations?
No. Rows inserted by a synthetic data job do not fire the table’s triggers, so seeding a table does not send emails or start workflows.
Can I tell generated rows from real ones?
Not automatically, so seed tables meant for demos and testing. A common pattern is to add a column such as "source" and describe it as always "synthetic".
What if I can only read the table?
Rows are written with your permissions, so you need to be able to add rows to the table.
100% customizable, code and all
Make Autessa Synthetic Data fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours