Tokens

actions that produce data — such as capture, process file, read barcode, and spreadsheet lookup — make that data available to subsequent actions via tokens a token is referenced by its action name in curly braces for example if you name a capture action "recto" then you can later reference that capture with {recto} some actions produce structured tokens with named attributes, accessible with dot notation for example a capture action named recto can be referenced as {recto path}, {recto name} this token system is how more complex pipelines are wired together without any scripting there are only a few uses for tokens in the currently available actions in the sequencer but as we add additional actions they will power more flexible workflows