Help Center Cortex AISet up

Build a complete system with the workspace builder

Describe your business in a sentence, and it asks only for what’s missing, then suggests a complete plan: units, fields, relations, stages, sample data, automations and documents. Edit it and approve, and it builds all of it or nothing.

7 minUpdated Oct 27, 2026

Open in Corteksa

Before you start · for owners

The permissions to create units and fields

You need: The permissions to create units and fields

Steps

In the assistant, type a description such as: “Build me a fire extinguisher maintenance system: clients, contracts, monthly visits, quotes”.

Answer the questions card if it shows, or type a message instead.

Review the plan card: the units and their fields, the relations, the sample data, and the automation and document goals.

Choose Edit plan to change the card directly, type the change in a message, or decline.

Choose Confirm & build.

A live list of steps shows: units, stages, fields, relations, views, sample data, folder, automations, documents.

Review the final summary; it’s worked out from your actual workspace and mentions anything missing.

What it builds

Each unit gets a status field with its stages, and the last stage is closed. A table view, and a Kanban if the unit has a select field. 3 sample records linked to each other. One folder in the sidebar.

A field named after something else in the system becomes a real relation. A field with the word “rate” or % is a number, not a currency.

People units, such as clients, get the messaging fields, so WhatsApp, Facebook, Instagram and TikTok records are created automatically.

If your workspace already has a unit with the same name, it’s used and not duplicated.

Automations and documents

Up to 4 automation goals and 2 documents in the plan; you remove the ones you don’t want. After the build, the suggested automations show for review: choose Switch them on, or Skip. Turning them on is your decision.

All or nothing

If the build fails or you stop it, everything it created is undone, and no unit that existed before is deleted. A failed automation or document goal doesn’t fail the build, and it’s mentioned in the summary.

Field types it plans with

Text, long text, number, boolean, date, date and time, start date, due date, select, multi-select, priority, rating, currency, email, phone, link, location, file, photo, catalog, serial number, calculation, lookup, rollup. Relations come from the relations section, and tags and status are added automatically.

If something goes wrong

What you see

Why

What to do

“The build failed, so I undid it — nothing from this plan was created”

An error during the build.

Ask for the build again.

“The build failed, and I could not undo all of it”

Part of what was created is still there.

Check the new units and delete the incomplete ones before building again.

“I couldn’t finish that build within the allowed number of steps”

The build is large.

Ask for the next part.

“No automations were created — your workspace is ready without them”

You chose Skip.

Build the automations yourself. See How do automations (workflows) work? The complete guide.

“That workspace is already built — there is nothing left to confirm here”

You approved twice.

Nothing to do.

A real example

Basma Clinics

The situation

The owner wants a ready system without building it by hand.

What they did

She wrote: “Dental clinics, bookings from WhatsApp, appointment reminders”.
She answered 2 questions, removed a document goal she didn’t need, then approved.

The result

The “Patients”, “Appointments” and “Treatments” units were built in minutes, with their relations and a bookings Kanban.

A made-up company, to show the idea. The numbers are rounded.