Hi and welcome to the Community, ​@Tobias_ADA! 

We have a Client Portal template that uses Zaps, Interfaces, Tables and Chatbots which you might find useful in getting started on this. You can learn more about the template and try it out here: https://zapier.com/templates/client-portal

We’ve also got a video guide that covers how to setup a client portal which I’ll share here too in case it helps:

Once you’ve got the portal set up you can have Zaps add/update information in the table which would then reflect in the information clients see in the portal. Knowledge sources for Chatbots can be set to automatically sync so you could have Zaps that update the data in the table (quickest sync is daily) so that the Chatbot is kept up to date with new information added to the table. 

Hope that helps to get you pointed in the right direction. If you run into any issues while setting it up or have any further questions at all just let us know! 

Yeah I’ve already set something up using that one but that  entirely misses my problem. 

“I want to create an interface that they can log into and access information, and different stuff related to them. Do I need to create the entire interface flow for every single client.”

I have -multiple- clients, each with different needs. I want to have the same base workflow for all of them, just with unique information per client. How can I set up so they use the same workflow with maybe a different table & chatbot connected?

Do I need  to have 8 of the same ‘client portal’ templates set up, one per client? Or can I use one, and then create different users, with unique tables connected?

Ah, sorry for missing that previously ​@Tobias_ADA. Didn’t realise you’d already got that part set up! 

The idea with that client portaI template is that it would be a single portal that is used for all clients. But if you want completely different tables connected for each client then you’d need to have different ones set up to display the content that would vary for each client. The interface pages could be set to show items within each component section that is relevant to the client, but the component sections can’t be conditionally displayed or connected to a certain table or chatbot depending on the client viewing it. That kind of functionality would be fantastic to have though! I’d recommend reaching out to the Interfaces team here to submit a feature request so they can look into getting that added. 

Hope that answers your question—let me know if you have any further questions or if there’s anything else you need help with!