Building a 3B workflow from a Tines export

You'll be handed a Tines story as a JSON export and asked to rebuild it in 3B. This guide tells you, for each Tines piece, what to build in 3B and how. Treat it as a starting map, not gospel: some mappings are unproven, so when something looks ambiguous (especially formulas, dates, and type coercion), flag it rather than guessing silently.

Flag these up front (not portable / needs human input)

• 5-minute (300s) per-step execution ceiling — there's no way today to run a step longer than that, so long running steps or delays need to be considered up front and broken up (durable state in a volume + cron continuation).

Always: write a migration report in the workflow README

After building, document the migration in the workflow README. Cover:

• Link back to the original - If the JSON export contains a story_url then include this at the top of the migration report as a hyperlink "View original story on Tines".
• What was migrated — the Tines actions and how each maps to its 3B step.
• What changed shape — anything that isn't a 1:1 port (fan-out → single-run loops, Implode → SQLite join, formulas → code), so the user knows where behavior may differ.
• What needs a human — flag everything you couldn't fully reproduce or that needs the user to finish: e.g. agentic AI actions, missing credentials, anything where a formula/date/type-coercion translation is uncertain.
• What to double-check — call out the silent-failure risks (missing fields, type coercion, cross-run dedup) so the user knows where to verify.
• Existing Tines dependencies — any calls back to Tines for Resources / Records etc. This will be important for the customer if they look to ever decommission their Tines Stories infrastructure and move fully to 3B.