Hi @Jmburke

Have you reviewed the available help articles for using PostgreSQL in Zaps?

https://zapier.com/apps/postgresql/help

Thanks Troy -- yes, I have been using the help documentation for general integration of postgres w/ Zapier.

I’m seeking out direction on how my platform might do one/both of the following

• Utilize the Zapier account of the client (so that it’s using “their Zap budget” and my platform is simply software solutions provider enabliing that based on the activity that’s happening in my platform
• Dynamically change the zap based on who the client is (ex: if new table row for clientId=X, then email joe@x.com; if new table row for clientId=Y, then email mary@y.com

Really trying to understand how others multi-tenant platforms have worked with Zapier 

Hi @Jmburke 

1. Utilize the Zapier account of the client (so that it’s using “their Zap budget” and my platform is simply software solutions provider enabliing that based on the activity that’s happening in my platform
   1. Your app would need to be authenticated in the client’s Zapier account
   2. OR
   3. Their Zapier account would need to send your app data, possibly via a webhook
2. Dynamically change the zap based on who the client is (ex: if new table row for clientId=X, then email joe@x.com; if new table row for clientId=Y, then email mary@y.com
   1. Options
      1. Filters: https://zapier.com/apps/filter/help
      2. Paths: https://zapier.com/paths
      3. Lookup Tables: https://zapier.com/help/create/format/create-lookup-tables-in-zaps

Oooh, paths and lookup tables might get my what I need related to doing diff’ things for diff’t clients

Regarding doing this on behalf of my clients (who also have Zapier), would these Zaps need to live in their Zapier account? I don’t want that as I’d want to maintain them in one place (versus deploy changes to them in each client’s account).

Aside the above issue, since these zaps would be triggered by activity in my app or my database, these Zap definitions are not things that I’d be able to expose to other Zapier accounts. is there no way for the triggering of a zap to be done using the “account ID,” where the Zap definition and management of those Zaps would be in my account, but the triggering of the zaps would be attributed to our mutual client?

@Jmburke 

Oooh, paths and lookup tables might get my what I need related to doing diff’ things for diff’t clients

NOTE: Paths are limited to 5 in a Zap.

You may want to consider chaining Zaps together with Webhooks: https://zapier.com/apps/webhook/help

Regarding doing this on behalf of my clients (who also have Zapier), would these Zaps need to live in their Zapier account? I don’t want that as I’d want to maintain them in one place (versus deploy changes to them in each client’s account).

If you want their Zapier account Tasks used when the Zaps run, then the Zaps will need to be configured in each client’s account.

Otherwise, I believe that may be against the Zapier Terms of Service:

(E) otherwise use the Service or Software outside of the scope of the rights expressly granted herein. You agree to use the Service and Software only for your own internal business operations, and not to transfer, distribute, sell, republish, resell, lease, sublease, license, sub-license or assign the Service or use the Service for the operation of a service bureau or time-sharing service.

Hey @Jmburke,

I just wanted to pop in here and confirm that Troy is correct. The Zaps would need to be in your client’s own Zapier account as discussed in this related thread:

 
Usually when a client connects to an app account using their own login credentials this will ensure that they only have access to the information in that app that belongs to them. So the login itself would limit what the user is able to access in the app/database. 

Hope that helps to clarify!