Workflow builder

Define the routine

Start by writing the job in plain language.

The routine should answer one question: what should CLEA do again later?

Do not start with automation. Start with the work. If the work is useful once, then you can decide whether it should become a workflow.

Reference files and folders

Workflows become stronger when they reference real workspace context.

That can be a workflow file, sitemap file, brand note, report, or hidden dashboard context file that CLEA can read.

Set expected output

Tell CLEA what to return.

This is the most important part. A workflow without an output becomes a vague chat. A workflow with a clear output can become a report, table, suggestion card, or page brief.

Define the routine

Write what CLEA should inspect.

Reference files

Add workflow, sitemap, or source files when needed.

Set output

Tell CLEA what to return.

Test manually

Run once before scheduling.

Choose trigger and schedule

A workflow can start from manual chat or from the calendar.

Try it manually first. If the result is useful, schedule it. If the result is weak, fix the file before scheduling it.

Inspect the result

Read the output before trusting it.

Check the evidence, the reasoning, and the suggested action. If a workflow creates a card or page task, make sure the action is supported.