Marvin A.

Hey there! You probably want to have them use the agent in their own account. You can simply copy the agent as template and share it with them. We did a call with one of our partners recently who talked a lot about how he serves his customers in case it’s helpful: https://www.youtube.com/live/SIY6sJaHUGc?si=UlpMbsj2NO_eUjTI 🙏🏾

Gotcha! Here we go :) https://www.youtube.com/live/SIY6sJaHUGc?si=UlpMbsj2NO_eUjTI

See message above 👆🏾

There you go! https://lindycommunity.slack.com/archives/C08J43ZE3GW/p1766003594867809?thread_ts=1765908374.541739&channel=C08J43ZE3GW&message_ts=1766003594.867809

There are plenty more approaches

Sure! Plenty of different approaches. One of them is finding 5 or so ICP profiles on Linkedin and then having your Lindy agent use Get LinkedIn Profile by URL . This will not only get their profile, but 10-20 lookalike profiles too. Then you can add an agent step to make sure it’s the right ICP → add to your list → rerun

Recording here: https://www.youtube.com/watch?v=tWGBTnfQKCE 🤝

Hey! Great questions, this is exactly what our Teams features are designed for. 1. Sharing & Reusing Lindies When you click “Share” on any agent, you get three options: Edit access (full editing + all tasks visible), User access (can run the agent, only sees their own tasks), or Template (creates a copy others can customize). This makes it easy to build a team library. 2. Builder vs. User Workflows “User access” is built for this. Non-technical teammates can trigger and interact with agents without any editing capability — perfect for chat-based agents or manual-run workflows. 3. Automation Handoff A few options: grant Edit access for maintenance handoff, use workspace migration if ownership shifts entirely, or share as a template if multiple people need their own version to maintain. For more details on all of this: https://docs.lindy.ai/account-billing/teams-collaboration Would love to hear how your workshops go in Korea!

Arvell C.! Just replied on X: https://x.com/webtotheflow/status/1972374907452350806?s=20 For this one it was just simplicity. It’s easier for me to manage everything in one. Also, since this is a pretty specific use case I didn’t bother at all about making the individual flows generic enough to be used for different use cases. :) For yours it sounds like you’d benefit from keeping them separate either in the same workflow builder (not one one workflow/agent) or in fully separate ones to make sure context is handled well

Thanh is LIVE!