Dynamic Tokens

Dynamic tokens let you build smart file paths and naming conventions that automatically adapt to each job’s properties at runtime.

Any value wrapped in square brackets (like [resolution]) is a dynamic token. When a workflow runs, Mistika Workflows replaces each token with the actual value for that job: the resolution of the source media, its frame rate, the current date, and so on.

Where you can use tokens

Tokens work anywhere you define a path or filename:

• Output folder paths. e.g. Deliverables/[resolution]/[codec]
• Output file names. e.g. [baseName]_[resolution]
• Input name conventions: to match or filter source files dynamically

Example

Say your output path is:

Volume/[resolution]/[baseName]_[framerate].mov

If the source clip is 1080p at 25 fps and named master_clip.mov, the resolved path would be:

Volume/1920x1080/master_clip_25fps.mov