Skip to content

Create your first Job

This walkthrough reads a public example page and creates no business record. You need Job editing and Toolbox permissions. Launching an ordinary Session also requires execution permission and available capacity.

  1. Select your project and open Jobs.
  2. Choose New Job.
  3. Enter Example page title and a short description.
  4. Review the inherited Robot kind. Choose Browser if a local override is needed.
  5. Use Create Job in the window’s title bar.
  6. Click the saved Job name to open Toolbox.

New Job form with an example name, description, inherited Browser settings and the Create Job command in the title bar.

The current New Job form with demonstration data. An inactive override switch means the displayed value is inherited. Creating metadata starts an empty scenario; it does not add actions.

Use the plus command below the tree. Choose an action, complete its fields and use Apply action. The action then belongs to the current scenario draft. Cancel discards the pending action edit.

Action Configuration
Navigate / gotoUrl Literal URL: https://example.com/.
Wait / wait Type: exists; time: 5000 milliseconds; CSS locator: h1.
Set / set Destination path: pageTitle; CSS locator: h1.

Keep these fields as literal text. The Set action extracts the heading into a working variable. Apply each action before selecting the next one.

  1. Follow the startup progress until Toolbox is ready.
  2. Use scenario Play.
  3. Confirm the example page appears.
  4. Inspect logs and values; pageTitle should be Example Domain.

This scenario has no loops, so the Debug switch does not change its three-action sequence. For loop-based Jobs, Debug advances outer loops one iteration at a time.

Toolbox retains its page and variables between commands. Playing only Set assumes the page is already open. Use the complete sequence to test its navigation and wait together.

  1. Use Save in Toolbox to persist the scenario.
  2. Open the Job’s ordinary launch command.
  3. Review the inputs and confirm.
  4. Open Sessions, inspect the resulting execution and review its outcome.

Apply action changes the current scenario draft. Save changes the stored Job. Launching a saved Job does not save an unapplied form or Toolbox draft. Next, replace changing literals with named inputs.