Open Settings (sliders icon in the editor header). Settings belong to the flow, not to a version.
| Setting | Stored as | Default | Meaning |
|---|---|---|---|
| Other flows can call it | setting.caller: "self" / "none" | none | Run flow nodes and error flows can use it. It needs a Flow input. |
| Error flow | setting.error.flowId | none | A callable flow that runs with the failure when a run of this flow fails. See Error flows. |
| Run time limit (hours) | setting.timeoutMs | 24 hours | A run that takes longer stops and fails. Time waiting for you counts. 0 = no limit (endless flows). Up to 7 days. |
| Keep files (days) | setting.file.ttlMs | 0 | A run's files (screenshots, downloads) are deleted this many days after it ends. 0 keeps them as long as the run (90 days). Up to 90. |
| Keep incomplete runs | setting.incomplete.isKeep | on | A node set to Save to resume later ends the run Incomplete, to go on from there. Off: it fails instead. |
| Offer as an MCP tool | setting.tool: { isEnabled, name, description } | off | MCP clients of the workspace's MCP server trigger can call this flow by name (letters, digits, _, -; empty: the flow's name), with its Flow input as the arguments. |
| Turn off after failures in a row | setting.failure.limit | 0 | This many failed runs in a row turn the flow's campaigns off (each counts its own main runs) and pause its Schedule trigger (its own real runs). You get a notification. A succeeded run resets the count. Publish again to turn a paused schedule back on. 0: never. |
| Timezone | setting.timezone (IANA) | UTC | Used by Schedule at, Date & Time and Wait until, unless a node sets its own. |
| Tags | tag | none | Comma separated, lower-cased; filter the Studio list by them. |
Test browser
Per browser name the flow's nodes act in (x, facebook…): the Studio tests and Open browser use. New browser (default) makes one on the first test, <flow> · <name>. Pick a campaign's browser to test with its sign-in; only browsers on the flow's engine are listed.
Options
What the flow asks for when it runs. A fills them; Studio runs use each option's default.
| Field | Meaning |
|---|---|
| Key | Its name, dotted keys nest: account.x is {{ option.account.x }}. |
| Kind | A dataset entry, dataset.account (Account, of a platform: 𝕏, Threads, Facebook or Shopee), dataset.ai (AI key) or dataset.post (Post set, see ): the same kind as the node field it fills, so a field lists the options of its kind. Or a value: Text, Long text (a multi-line text box, for AI criteria and prompts), Number, Duration (a number and a unit: minutes, hours, days; kept in ms, so {{ option.post.wait.minMs }} is 10800000 for 3 hours), Yes or no, Choice (a list you type), List (several entries the campaign adds, edits, reorders and removes itself, e.g. searches; the Default is one entry per line), Limit (Set here: one or more lines of N per period, every one at once, or Follow the account: the account's own limit; its value is { mode, window }, read as {{ option.pace.limit.mode }} and {{ option.pace.limit.window }}). |
| Default | For an account or AI key: the one Studio runs use. For a value: the value when the campaign leaves it. |
| Required | A campaign can't be saved without it. |
| Label, Description | What the campaign form shows for it (the key when there's no label). |
| Group | The campaign form's tab it sits in, e.g. Accounts, Collect, Reply. Empty: Accounts for account and AI key options, General for values. |
| Show when | Show it only while other options hold certain values, e.g. Search for only when Where to look is search. Press Show when… to add a rule: pick a Choice or Yes/no option and the values (a comma list, or Yes/No). Several rules must all hold. Or… starts another group of rules: the option shows when any one group holds (e.g. the AI key: when the AI writes, or when a Shopee search needs it). A hidden option isn't asked on the campaign form, isn't required or checked, and the flow reads its default. |
Use them in any field: {{ option.collect.max }} in Collect posts' "Maximum posts", {{ option.collect.author }} in its "Same author again", {{ option.account.x }} in every 𝕏 node's account, {{ option.ai }} in every AI node's AI key, and in node settings such as a : {{ option.pace.limit.mode }}, {{ option.pace.limit.window }}. The 𝕏 Auto Reply template comes with:
| Key | Group | Label | Used by |
|---|---|---|---|
account.x | Accounts | 𝕏 account | Sign in, Reply |
ai | Accounts | AI key | Every AI node's AI key |
collect.max | Collect | Posts per round | Collect posts › Maximum posts |
timeline.language | Collect | Post language | Collect posts › Language |
collect.author | Collect | Same author again (never · day · allow) | Collect posts › Same author again |
pace.limit | Pace | Reply limit (Set here or Follow the account) | Reply › Settings › Limit |
Account fields must use an account option and AI key fields an AI key option; Node details lists the options that fit.
Account options give the flow its accounts and AI key options its AI keys, so each campaign picks its own; the browsers belong to the campaign (see ). A called flow's options are filled by the same keys: Auto Reply and Auto Post declare account.shopee themselves (shown only with Shopee on), so the campaign form asks for it once, in their Accounts tab, and one ai fills both flows' AI nodes. A key the calling flow already declares isn't asked again for the called flow.
Timezone
When a run starts, every node with an empty timezone field gets the flow's timezone, and the scheduler reads Schedule's at in it. A called flow uses its own timezone.
Example: timezone Asia/Jakarta, Wait until 00:05 → the run waits until 00:05 WIB (17:05 UTC the day before).
Agent instructions
The agent panel has Instructions for this flow: text the keeps in mind in every conversation about this flow (accounts to use, tone, language, things to avoid). Stored as setting.agent.instruction.
Stars
Star a flow from the Studio list (Star / Unstar) and filter with Starred only.
FAQ
My endless flow fails after 24 hours.
Set Run time limit to 0.
Why does my old flow fail with "must use an account option"?
Account fields now come from options. Add an account option in Settings › Options and pick it in each account field.
Why does my old flow fail with "must use an AI key option"?
AI key fields come from options too, so a campaign can pick its own key. Add an option of kind AI key (key ai) in Settings › Options, set its default, and pick it in each AI node's AI key field (and Fallback AI key, if you use one).
Can a flow be its own error flow?
No: A flow can't be its own error flow. The error flow must start with Flow input and allow callers.