Lindy Community Icon

Enhancing Workflow Portability: Best Practices and Suggestions

·
·

Rogier H. Totally feel you on this, Rogier — I’ve run into the same thing. The share function is great for quick duplication, but yeah, missing config in nodes like Google Sheets, Outlook, and cron makes it tough to fully reuse. What I’ve been doing as a workaround:

  • I keep a private “template vault” with notes on key node configs that don’t carry over.

  • For things like recurring schedules, I drop a reminder inside the workflow via a text node just to flag what to reconfigure manually.

  • I’ve also tried exporting/importing workflows via JSON when possible, though still a bit manual.

Would love if Lindy eventually supports full config portability — +1 to any feature request for this!