Skip to main content

Recording Workflows

This guide explains how teams typically use the XY Browser Agent to record a task, save it as a workflow, and review it afterward.

What recording is best for​

Recording is a strong fit when:

  • a task happens in a browser portal
  • the task follows a predictable path
  • people are currently doing the same clicks and entries over and over
  • the system does not offer a practical native integration

The basic recording flow​

1. Start with a clean task​

Pick one task with a clear start and finish, such as:

  • checking a claim or referral status
  • entering information from a document
  • downloading a report
  • uploading a file into a portal

2. Start recording​

Open the Browser Agent, start a new recording, and choose the recording options you want to capture.

3. Perform the task normally​

Work through the task the same way you would if you were doing it manually.

Good recordings are:

  • deliberate
  • consistent
  • easy to understand later

4. Stop and save​

Once the task is complete, stop the recording and save it with a name your team will recognize.

What happens after you save​

After saving, the workflow can be reviewed in the Browser Agent and, depending on the experience your organization uses, in the XY Web App as well.

This is where teams usually:

  • replay the workflow
  • review the recorded steps
  • check whether any cleanup is needed
  • decide whether to make the workflow more reusable

Reviewing the recording​

When you review a saved workflow, look for:

  • unnecessary clicks or navigation
  • steps that depend on one exact value
  • places where a variable would make the workflow more reusable
  • spots where a person may still need to review the result

Recording tips​

Keep the first version simple​

It is better to capture one short workflow cleanly than to over-record a long and messy one.

Use realistic but safe data​

Record with data that reflects the real process while still being appropriate for testing and validation.

Name workflows clearly​

A good name should tell a teammate what the workflow does and when to use it.

Replay early​

Run the workflow soon after recording so you can catch issues while the steps are still fresh in mind.

Where recording fits in the bigger workflow story​

A recorded browser workflow is often just one part of a broader automation. Teams commonly combine it with:

  • files from Files
  • connected systems from Integrations
  • agent-driven steps inside a larger XY workflow