Schedules, Surveys & Workflows

Job templates run on demand, but AWX can also run them on a timer, ask the user questions first, and chain many jobs into one flow. ⏰

Add a schedule to a job template and AWX launches it automatically, nightly backups or hourly drift checks, with no human present.

Schedules use calendar RRULE recurrence rules, so you can express things like every weekday at 2 AM or the first Monday each month.

A survey turns a job template into a simple form, prompting the launcher for values like a hostname or version before the job runs. 📝

Each survey answer is fed into the play as an extra variable, so non-experts safely supply input without ever editing YAML.

Survey fields can be text, password, multiple-choice or integer, and marked required, so AWX validates input before the job even starts.

Schedules plus surveys give teammates self-service: they fill a form and click Launch to do real work, with zero command-line knowledge. 🙌

A workflow template links multiple job templates into a graph, so deploying app, db and proxy becomes one orchestrated, ordered run.

Workflow nodes can run a next step on success, on failure, or always, letting you build cleanup or rollback paths into the flow.

A workflow can chain job templates, project syncs, inventory updates and even approval nodes that pause until a human signs off.

Attach notifications so a finished schedule or workflow pings Slack or email on success or failure, keeping the team informed automatically. 📣

What lets a person supply input to a job through a simple form?

Schedules run jobs on a clock, surveys collect input as variables, and workflows chain jobs with branching, turning AWX into self-service orchestration. ✅