EmbodiFlowDocs
Get startedDataWorkflows and algorithmsTraining and deploymentDeveloper reference
  • Workflows and algorithms

Workflows

  • How workflows work
  • Build your own workflow
  • Runs and logs

Algorithms

  • Algorithm catalog
  • Write a custom algorithm

Algorithm developer guide

  • Your first algorithm
    • Standardize
    • Check
    • Transform
    • Enrich
    • Segment
    • Curate
    • Export
  • Image algorithms
  • Use your algorithm in a workflow
  • Interface reference
  • SDK reference
  • Command line
  • MCP tools
  • Troubleshooting

© 2026 EmbodiFlow

llms.txtOpenAPI JSON
  1. Workflows and algorithms
  2. Workflows
  3. Build your own workflow

Build your own workflow

Duplicate an official workflow, drop in an algorithm, publish it and test it on a real recording, without writing YAML.

The fastest way to a workflow of your own is to start from an official one and change what you need. Here you add one algorithm to the robot workflow, publish it and watch it run on a real recording. It takes a few minutes, and the editor stops you from wiring anything wrong along the way.

You need to be an Owner or Editor of the project the copy goes into.

1Duplicate a template

Open Workflows. On an official template card, such as Robot standard, click the ⋯ button and choose Duplicate to edit. In the dialog, give the copy a name and choose the project it belongs to.

Switch off Use this copy for the project workflow if you want to edit first. Left on, it publishes the unedited copy straight away and replaces the project's processing workflow. Then click Create copy.

2Look around the editor

The editor opens on your copy with the chips Draft r1 and Saved, and Problems (0) at the top. On the left is the algorithm library, grouped by category. The built-in algorithms are there, and so are your team's, marked Team.

3Drag an algorithm in

Type in Search algorithms to find the one you want, then drag its card onto an empty part of the canvas. The editor connects it for you: it finds outputs that fit the new step's inputs, and inputs that take its outputs. A message such as "Added Motion energy and made 2 connections." confirms it, with Undo next to it.

If nothing fits, the step is added unconnected. Drag from an output dot to an input dot to wire it yourself.

4A wrong connection is refused

Try to join ports of different types, for example a Checks output to a Recording input, and the wire simply isn't made. A short message next to the step tells you why: "Checks cannot connect to Recording." The editor also refuses a connection that would make a loop, and one that would use a recording before it's anonymized.

5Fix what the Problems panel lists

Some mistakes only show up in the whole graph, such as a required input left unconnected or two steps writing the same feature. The Problems button at the top counts them and turns red. Click it to open the panel: each problem names the step and says what to fix in plain words, with technical details underneath.

Publish stays disabled until the count is back to zero. Fix the step, or select it and delete it.

6Set parameters in the inspector

Click a step to open it on the right. Under Settings, each parameter shows its default and its allowed range, such as "At least 1". Change a value and the step on the canvas shows it as a small chip, for example "Frame step: 2". The circular arrow next to the field puts the default back.

7Publish

Click Publish at the top right. The dialog Publish this revision lists what changed under Structure, or line by line under YAML diff. On a first revision every step reads "Added", which is expected. Click Publish, and the chip changes to Published r1.

8Test on a sample

Click Test on sample. In the panel at the bottom, choose a project and tick up to three recordings. You can also set Window in seconds to run only the start of each recording, up to 600 seconds. The panel estimates how long the test takes, and how many steps it can reuse from an earlier test.

Click Run test, then Open the run.

9Watch the run

The run page shows your graph with each step filling in as it runs, until the run reads Succeeded. With a window, the steps that save results, such as Save results and Evaluate, are skipped on purpose: "Skipped: a test run on a window saves no result." They stay grey, because skipped is never a pass.

Use it for the project

When you're happy with the result, open the project's Workflow page, click Change workflow and choose your published workflow. From then on, new uploads run through it. Recordings that were already processed keep their results.

Need an algorithm that isn't in the library? Write a custom algorithm in the browser. Once saved, it appears in the library ready to drag in.

Next

  • Runs and logs
  • Algorithm catalog
  • Write a custom algorithm
Previous

How workflows work

Next

Runs and logs