Teach once or describe in chat: two ways to hand a job to Operon

You can start an Operon job by describing it in plain words or by showing it once. When to use each, and how both end up as a reusable skill.

Operon team2 min read

There are two ways to give Operon a job. Both end in the same place, a skill you can run again, but they suit different jobs.

Describe it in chat

Type the job the way you would explain it to a colleague:

Open the supplier portal, go to Orders, filter to last week, and save order number, status and amount as a CSV.

Attach any files the job needs. Operon plans the steps, opens a real browser and starts working. You watch it live in the chat and can step in at any time.

Describing works best when:

  • The job is clear in words: which site, which page, what to read or fill.
  • The site is reasonably standard, with labelled fields and buttons.
  • You want to get going right away.

Tips for a good description:

  • Name the site and the page.
  • Say exactly what to read or fill, and in what format you want the result.
  • Mention where to stop if it matters, for example “stop before Submit”. Operon pauses before final actions anyway.

Show it once

Some jobs are easier to show than to explain: a portal with odd menus, a sequence of tabs, or a field whose meaning is only obvious when you see it. For those, you can do the job once yourself while Operon watches and records the steps.

Showing works best when:

  • The path through the site is unusual or hard to describe.
  • The exact order of clicks matters.
  • You already do this job by hand and just want to stop doing it.

Either way, save it as a skill

When a run works, save it as a skill. Operon keeps the exact steps that worked and what inputs changed, such as a vehicle number or a date range.

From then on:

  • Replays don’t need the AI. They follow the saved steps, so they are faster and much cheaper than a fresh run.
  • Inputs can change. Run the skill again with a new file or new values.
  • Schedules are one click away. Run it every morning, every Monday or on the 1st of the month.
  • Changes are handled. If a page changes and a step fails, Operon fixes that step with the AI and asks you whether to keep the fix.

Which should you pick?

Start by describing. It is the quickest way to find out whether a job suits Operon. If the run gets lost on a tricky portal, show it once instead. Either way, save what works, because the second run is where the time and cost savings start.

See use cases for examples, or start free.

More from the blog

2 min read

Automating portal work when there is no API

Most business portals have no API or import. A practical look at your options, from manual work and scripts to RPA and AI computer workers, and how to pick the first job to automate.

Read post
2 min read

How Operon keeps you in control: safety pauses, the vault and live view

Handing web work to an AI raises fair questions. Here is exactly when Operon stops and asks, how your logins are stored, and how you can watch and take over any run.

Read post
Free trial

Hand off your first job today

Sign up, describe a browser job you do every week, and watch Operon do it. Save it as a skill when it works.