Skip to main content
Figranium tasks accept typed variables and reference them inside action values with a {$name} template. The Python SDK ships a variable() helper that produces the correct token, plus typed shapes for declaring variables on a Task.

Declare task variables

Task variables live under task["variables"]. Each entry has a type and a default value.
Variable type is "string", "number", or "boolean". Additional fields are allowed on each variable entry, and unknown fields are preserved by the SDK’s flexible task type.

Reference variables in actions

Anywhere an action expects a string value, use variable(name) to reference a task variable. The helper returns {$name}.
variable("") raises ValueError; names must not be empty or whitespace-only.

Override at runtime

Pass variables when executing a task to override the defaults for a single run. Runtime variables use plain values, not the typed shape used at declaration time.
You can also pass taskVariables, which sets task-scoped defaults for the run without changing the saved task.

Direct execution

scrape, agent, and headful accept the same runtime variable shape when called directly:
See Execution resource for full input shapes.

Auto-created variables

Some server-side flows auto-create variables (for example when a script writes a result to a new name). Those entries include "autoCreated": True. The SDK preserves the flag on read and write.
Use variable() for every template reference so your code stays type-safe and refactorable. Hard-coding {$name} strings is brittle when variable names change.

Actions

Every action helper that accepts a template value.

Tasks resource

Full reference for saving and running tasks.