Variables and inputs
Workflow inputs let you parameterize a workflow so it can be reused with different values. They're declared in the Inputs section and referenced in step text with double-brace syntax: {{topic}}{{brand}}{{campaign_name}}
Defining an input — each input has a name (the variable key), a label (what the user sees), a type (usually text), and a required flag. Required inputs must be filled in before a run can start.
Using a variable in a step — anywhere in a step description, write {{topic}}
When to use an input vs. bake it in
- Use an input when the value changes per run — the topic of the blog post, the week to analyze, the client being reviewed.
- Bake it in when it never changes — your brand name, your domain, your tone of voice. Hard-coding stable values keeps the run form short.
Scheduled runs and inputs — when a workflow is scheduled, Magister uses the last-saved input values. If your scheduled workflow needs a value that genuinely changes week to week, consider putting "this week" logic into the step description instead ("pull data from the last 7 days").
Required inputs and run buttons — if a workflow has required inputs, clicking Run opens a form. The run doesn't start until every required field is filled.