Skip to main content
FlowFn
IntegrationsTemplatesPricingDocsBlogSign inStart free
All documentation

v1.53.0

UpdatedJun 15, 2026Reading time1 min read

Released 2026-06-15. Transfer an app — or a single item — to another team you administer.

Added

  • Transfer a whole app to another team. An app's Danger zone has a new Transfer to another team action. Pick a team you also own or admin, review a pre-flight summary (how many items move, which team connections / AI keys / approval assignees get cleared, and any plan-limit warning), and confirm. The app and everything inside it — workflows, forms, visualizers, agents, playgrounds, streams and their environment variables — move together. Public webhook and API URLs keep working.
  • Transfer a single item. Workflows, forms, visualizers, agents, playgrounds and streams each get a Transfer to another team action on their grid — pick the destination team and app, review, confirm. The item and its own environment variables come with it; it uses the destination app's shared variables, and links to other items left behind (e.g. a stream binding, an agent's workflow trigger) are flagged so you can move those too or reconnect them.

Notes

  • Team-specific connections are cleared. Platform-tool connections and AI keys belong to a team and can't follow the item — the pre-flight summary counts them so you can re-connect them in the destination team afterward. Approval assignees who aren't members of the destination team are removed.
  • Over-limit destinations. If the destination team is at its plan cap for that kind of item, the item still arrives but is flagged over plan limit (paused) until the team upgrades or frees a slot.
  • Authorization & audit. You must be an owner or admin of both teams; the transfer is immediate and recorded in both teams' audit trails.

Spotted an issue or have feedback?

support@flowfn.com
Back to docs hub →