Skip to main content

Workflows

The Workflows area is where teams manage the automations they run in XY. It brings together workflows created in the web app and workflows that started as browser recordings.

Main workflow views

My Workflows

My Workflows is the main home for workflows your team has configured in XY.

This is where users typically:

  • review existing workflows
  • search by workflow name
  • open workflow details
  • rename or organize the workflows they use regularly
  • create a new workflow, if they have access

Recorded Workflows

Recorded Workflows is for workflows captured with the XY Browser Agent.

This view is useful when your team:

  • records repetitive portal work
  • reviews saved browser automations
  • replays a recording
  • refines a browser workflow before broader rollout

How workflows are created

There are two common starting points:

Build in the web app

Some workflows begin directly in the XY Web App. This is common when the process depends on:

  • connected integrations
  • uploaded or synced files
  • workflow logic defined by your team

Start from a browser recording

Other workflows begin with a browser recording made in the XY Browser Agent, then become reusable recorded workflows that can be reviewed and improved over time.

What workflows usually connect

A single XY workflow may connect several product areas:

  • Agents for task-specific automation
  • Integrations for system access
  • Files for inputs, reference materials, and outputs
  • Browser Agent for work that happens inside a website or portal
  • human review when an exception needs attention

Workflow lifecycle

Most teams use workflows like this:

  1. Create or record the workflow.
  2. Test it on a small, safe example.
  3. Review the output and any exception handling.
  4. Refine the steps or inputs.
  5. Reuse it for repeated work.

Best practices

  • Start with one clear business outcome per workflow.
  • Keep early workflows narrow and easy to test.
  • Use recorded workflows for portal work and integrations for supported system connections.
  • Include human review when the process involves judgment or risk.
  • Revisit workflows after rollout so your team can simplify or strengthen them.