Best answer

What is the best practice to roll out Zap needing MS Teams Auth to our multiple customers

  • 26 February 2020
  • 4 replies
  • 120 views

Userlevel 2

Hi There,

Howdy Community !

This is my first post in this space and I am excited.


We are looking into Zapier to create POC with MS Teams integrations.

We are almost there with the POC and now thinking that Zapier can be a potential solution to go-live for our customers.


We are thinking to subscribe for either Team or Professional Plan and we need your help in making the right decision.

Our scenario is as follows,

we will build a Zap which sends message into a channel in MS Teams. This Zap is to be rolled out to all our customers (each customer has multiple users).


However, we have few questions on the design of the production solution.

Below are few,

1. What is the ideal-way to roll out the sing-in of MS Teams of the Zap to our customers ? How to handle multi-customer scenario of Zaps ?

2. Noticed this condition under a Plan "1min Update Time", where does it apply ?

3. What is a workspace in Zapier ?


Thanks.


Cheers,

Head of Engineering,

Praneeth G.


icon

Best answer by jesse 26 February 2020, 20:40

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Userlevel 7
Badge +10

Hi @Praneeth

You'd basically have to give each company your Zapier login details so they can then connect their MS Teams account - obviously this won't be idea for you.

Also, you should be aware that Zapier has anti-reselling rules which this may fall foul of (perhaps @Danvers can clarify?).

If either of the above are true, then the best approach is for you to have a Team account and for all clients to have their own account, which can then be connected to your account. You'd have a template zap which you'd deuplicate and share into each new client's account - they'd then login and connect MS Teams


Userlevel 7
Badge +9

Hey @Praneeth just stepping in here! If all of your customers need to utilize a Zap, we recommend they build it on their own Zapier accounts. It's going to be rather difficult to set this up on your own account as each customer will still need to authenticate their MS Teams account like @AndrewJDavison_Luhhu said.

Perhaps you can develop a help doc or other learning resource that would instruct your customers on how to build common Zaps with your service? Zap templates are another option to help folks get up and running faster: https://zapier.com/developer/zap-templates/

As for "workspaces", we have folders/folder permissions for Teams accounts and for Company accounts, you'll have the ability to have multiple teams in an account. Here is more info on that: https://zapier.com/help/account/companies/whats-the-difference-between-zapier-for-companies-and-zapier-for-teams


Userlevel 2

Thanks @AndrewJDavison_Luhhu and @jesse for your replies.

Andrew, on a high-level, it makes sense to give each client their own Zapier Team account.

We have variety of clients and its not a solution for us to instruct our client to build common Zaps. The idea is that we do all heavy-lifting for our clients and there is minimal intervention from their side.

If we create a Team account to each of our client, is there anyway to make read-only Zap for all our clients, coz we dont want our clients to play with Zaps ?

Is there any way to plugin this Zapier window into our product (web application), i.e. in an iframe or any other custom solution ?

@AndrewJDavison_Luhhu From your reply, the Template Zap which we duplicate for each Team account, can we make this as a base Zap i.e. any future changes in this Teamplate Zap would reflect in all our client Team account Zaps or do we need to roll out to each Team account again ?


Thanks in advance for your time ! :)


Userlevel 7
Badge +10

Hi @Praneeth

So you could have all the client's Zapier 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 the create shared folders for all these accounts, make 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.