Skip to main content
The Editor is Sequentum’s hand-authoring environment for Agents. It’s the escape hatch — most users start with Agent Builder and only reach for the Editor when they hit something Agent Builder can’t yet generate. Reach for the Editor when:
  • You need a custom script step (C# / JavaScript) inside the agent.
  • The site has navigation Agent Builder can’t reliably plan — multi-step auth flows, captchas needing human handoff, conditional logic across pages.
  • You’re migrating an Agent from Sequentum Enterprise — those convert directly into Editor agents.
  • You’re using a niche command that Agent Builder doesn’t surface yet.
If none of these apply, use Agent Builder. It’s faster and the resulting Agents are easier to maintain.

​
The command tree

An Agent in the Editor is a tree of commands. Each command does one thing — open a URL, click an element, paginate, extract a field. Children execute in order; repeaters loop their children. 
Agent
├─ URL         "https://example.com"
└─ Link Repeater (".product-card a")
   ├─ Page Action: scroll
   ├─ Action: click ".load-more"
   └─ Data List
      ├─ Field: name   ".title"
      ├─ Field: price  ".price"
      └─ Field: sku    "[data-sku]"
See the Commands reference for every command. The full per-command reference is being expanded in v1.x — for now, the legacy Sequentum Cloud Manual has detailed pages for each command.

​
Migrating from Sequentum Enterprise

Most Enterprise agents convert directly. Export the agent text from Enterprise, then import it via Control Center or POST it through the API.
A consolidated “Migrating from Sequentum Enterprise” guide is coming. In the meantime, see Upgrading to Sequentum Cloud and Converting Enterprise Agents on the legacy site.