# Workflow compiler brief table

Fill this before asking AI to generate an n8n workflow. A blank cell is not a detail to handle later; it is an instruction you are about to let the model improvise.

| Field | What you decide before generation | Example |
|---|---|---|
| Business job | The plain-language outcome | Turn a new estimate request into a reviewed follow-up task |
| Trigger | The exact event that starts the run | New form submission from the website quote form |
| Source records | The systems and fields the run may read | Form fields, company name, existing CRM account status |
| Destination records | The systems and fields the run may create or update | Draft task in CRM; no contact update |
| Credential owner | The named owner of every credential the workflow uses | RevOps owns CRM credential; marketing owns form webhook |
| Allowed changes | The maximum state change the generated workflow may make | Create draft task only; never assign owner automatically |
| AI-filled fields | Parameters the model may fill, with allowed values | Lead type in {new, expansion, partner}; urgency in {normal, rush} |
| Hard validation | Conditions that must pass before any write | Company domain must match one CRM account or stop |
| Stop condition | What sends the run to a person instead of continuing | Multiple CRM matches, missing email, high-value account |
| Test packet | The examples used before activation | Five redacted submissions: normal, duplicate, missing data, VIP, spam |
| Run record | The evidence kept for each execution | Input ID, selected account, proposed task, validation result, reviewer |