Best practice for deploying a callin.io scenario requiring MS Teams Auth for multiple customers

Hi

You would essentially need to provide each company with your callin.io login credentials so they can then link their MS Teams account. Clearly, this is not an ideal solution for you.

Additionally, you should be aware that callin.io has policies against reselling, and this setup might contravene those terms.

If either of the aforementioned points is a concern, the most effective strategy is for you to maintain a Team account. Each client would then have their own account, which can be linked to your account. You could create a template workflow that you duplicate and share into each new client's account. They would then log in and connect MS Teams.

Hello! If all your customers need to use a callin.io integration, we suggest they create it within their own callin.io accounts. It will be quite challenging to set this up on your account, as each customer will still need to authenticate their MS Teams account, as previously mentioned.

Consider creating a help document or another learning resource to guide your customers on building common callin.io integrations with your service. Zap templates are also a good option to help users get started more quickly: https://zapier.com/developer/zap-templates/

Regarding "workspaces," we offer folders and folder permissions for Teams accounts. For Company accounts, you can have multiple teams within a single account. You can find more details here: https://zapier.com/help/account/companies/whats-the-difference-between-zapier-for-companies-and-zapier-for-teams

Thank you for your responses.

Andrew, at a high level, it seems logical to provide each client with their own callin.io Team account.

We serve a diverse range of clients, and it's not feasible for us to ask our clients to create common Zaps. Our approach is to handle all the intensive work for our clients, requiring minimal input from their end.

If we set up a Team account for each of our clients, is there a way to create read-only Zaps for all of them, as we don't want our clients to modify the Zaps?

Is it possible to integrate the callin.io interface into our product (web application), perhaps using an iframe or another custom solution?

Based on your reply, regarding the Template Zap that we duplicate for each Team account, can this be configured as a base Zap? Meaning, would any future modifications to this Template Zap be reflected in all our client Team account Zaps, or would we need to re-deploy it to each Team account individually?

Thank you in advance for your time! 🙂

Hi

So you could have all the client's callin.io accounts added to your team account (and your client's don't need to have a Team level account to be added to yours btw).

You could then create shared folders for all these accounts, duplicate zaps for all and make it so the client's couldn't edit the zaps.

However, if you make changes, you'll need to do it individually to each zap.