DocsWorkflowsComponentsMachinemachine:extension:sequence

machine:extension:sequence

Runs an ordered list of library fragments in the connected browser extension as one logical job (one tab/session, one cancelable id) and blocks until the per-fragment results come back. Use it when fragments must share a live browser session; when they are independent, prefer chained machine:extension:run steps so the pipeline owns the control flow between them.

Options

Name	Type	Description
`refs`	`[]ExtSequenceRef`	The ordered library fragments to run as one job in the same browser session
↳ `workflow_id`	`string`	The id of the library fragment
↳ `variables`	`map[string]any`	Values scoped to just this fragment, merged over the sequence-wide bag
`client_id`	`string`	The extension client to run against, a hint the host may honour; empty leaves the choice of browser to the host
`variables`	`map[string]any`	Sequence-wide values injected into every fragment
`continue_on_error`	`bool`	Keep running later fragments when one fails
`timeout_ms`	`int`	How long to wait for the whole sequence before failing (default 10 minutes)

Outputs

Name	Type	Description
`ok`	`bool`	Whether every fragment finished without error
`stored`	`map[string]any`	The merged store outputs of all fragments, later fragments winning on name clashes
`workflows`	`[]WorkflowResult`	The per-fragment results in run order
↳ `workflow_id`	`string`	Is the id of the workflow this result belongs to.
↳ `ok`	`bool`	Reports whether the run succeeded.
↳ `steps`	`[]StepResult`	Holds each step's result, in run order.
↳ `step_id`	`string`	Is the id of the step this result belongs to.
↳ `type`	`string`	Echoes the step's action type.
↳ `ok`	`bool`	Reports whether the step succeeded. Skipped steps are always ok.
↳ `skipped`	`bool`	Is true when the step's condition was not met, so it neither ran nor failed.
↳ `format`	`string`	Names the shape Data is in.
↳ `data`	`any`	Is the step's extracted output, if any.
↳ `truncated`	`bool`	Says the step's own cap clipped its output, which is how a structured list read reports that the page held more items than it returned.
↳ `file`	`CapturedFile`	Carries the bytes a capture step took. The extension lifts it onto a dedicated file message before the result is streamed, so it is normally nil by the time a result reaches this side.
↳ `filename`	`string`	Is the file's name, after any step-level rename.
↳ `mime`	`string`	Is the file's content type.
↳ `size`	`int`	Is the byte length of Data.
↳ `data`	`[]byte`	Is the raw file content. It rides the JSON wire as base64, which encoding/json applies to a byte slice automatically, so neither side of the contract ever names the encoding.
↳ `error`	`string`	Describes the failure when OK is false.
↳ `started_at`	`int64`	Is when the step began, in Unix milliseconds.
↳ `finished_at`	`int64`	Is when the step ended, in Unix milliseconds.
↳ `stored`	`map[string]any`	Holds the values the workflow's store steps captured, keyed by store name, so a sequence chains one fragment's output into the next and a caller can read them.
↳ `error`	`string`	Describes what stopped the run when OK is false.
↳ `refused`	`bool`	Says the browser declined the work rather than attempting it, which is what a browser set not to run for this app answers. It is separate from OK because a caller repairs a broken fragment and asks a person about a refusal, and the two must not read alike.
↳ `started_at`	`int64`	Is when the run began, in Unix milliseconds.
↳ `finished_at`	`int64`	Is when the run ended, in Unix milliseconds.

Example

name: Fetch a bank statement in one browser session
actions:
  - name: statement
    component: machine:extension:sequence
    vars:
      refs:
        - workflow_id: swedbank-01-login
        - workflow_id: swedbank-03-open-statement
        - workflow_id: swedbank-04-save-files
      variables:
        user_id: "{{ var.user_id }}"
        date_from: "{{ var.date_from }}"
        date_to: "{{ var.date_to }}"

outputs:
  stored: "{{ statement.stored }}"

Edit or read the source on GitHub