Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.twine.se/llms.txt

Use this file to discover all available pages before exploring further.

Runs a pipeline step — the named unit of work that talks to a source or target system (e.g. “Load all employees”, “Save changes”, “Get one project”). Most flows are built around Flow Actions with transformation and control-flow nodes in between.

​
Configuration

  • Step — pick the step to run. Grouped by system in the picker; internal steps live in the “Internal” group.
  • System integration — which tenant’s credentials the step uses. Required for steps that call remote APIs, ignored for local steps.
  • Step options — typed form rendered from the step’s declared options. Defaults are materialized the first time you pick the step; cleared fields stay cleared.
  • Cache mode — Default reuses results from earlier in the same run when the step supports caching; Force busts the flow cache and asks the system to refresh any upstream caches it exposes.
  • On error — what happens if the step fails:
    • Halt flow (default): stop the whole run.
    • Halt branch: stop this path only; parallel paths keep going.
    • Continue: log the error and keep running. Most useful for best-effort sync actions.

​
Tips

  • Steps declare what they read from token.opts and what they write to token.assigns. Downstream Flow nodes read those assigns by name.
  • Steps that write to an assign show the assign in the Evaluator and Settings panes so you can pick what to persist per run.

​
Ports