Custom Workflows are reusable procedures saved as files. They turn your best practices into executable definitions that Dexter follows consistently — any team member can trigger a workflow by name and get the same reliable result.
Creating a Workflow
Walk through a process with Dexter once, then ask it to save the procedure:
- “Save this as a workflow called weekly quality audit”
- “Create a workflow for onboarding new production data”
Dexter asks what the workflow should do, creates the definition, and optionally includes supporting scripts for data transformation steps. Each workflow contains a set of instructions with a name and description, plus optional supporting files (documentation, Python scripts, shell scripts, config files).
Triggering a Workflow
- Explicitly — “Run the weekly quality audit workflow”
- Implicitly — if your request matches a workflow’s description, Dexter recognizes it and follows the saved procedure automatically.
- From scheduled jobs — workflows can be referenced by scheduled jobs for recurring execution.
Built-In Workflows
ProDex includes built-in workflows for common operations (data pipelines, simulation modeling, experiments, report generation). Custom workflows you create appear alongside these in the Custom Workflows section of the left sidebar.
When a process that used to take a senior engineer an hour to explain becomes a workflow, any team member can trigger it by name and get the same reliable result.
