How to set up dual account authentication in Zapier CLI application

Other Questions Zapier
1

I’m working on a Zapier CLI app and need to allow users to authenticate with two different accounts simultaneously. I’ve noticed that some existing apps on the platform offer this functionality, but I can’t find clear documentation or sample code showing how to implement this feature.

When I check the authentication setup, it seems like the standard configuration only accepts a single auth handler:

const MyApp = {
  version: '1.0.0',
  platformVersion: '10.0.0',
  authentication: userAuth,
  triggers: {
    // trigger definitions
  }
};

Is there a way to configure multiple authentication flows so users can link two separate accounts to the same app? What’s the recommended approach for handling this scenario?

2

Zapier CLI doesn’t directly support this through the standard auth object - each authentication creates one connection per app instance. But there are a few workarounds that work well. First option: create separate app versions or add connection labeling to your auth flow. Add custom fields in your auth config so users can specify which account type they’re connecting. Then handle the routing in your API calls based on those connection parameters. Second option: use REST hooks where users set up multiple connections to the same app but configure them differently during auth. You’ll need to modify your authentication test function to validate and store account-specific identifiers. The main thing is managing connection state properly so your triggers and actions know which account context they’re working with.

3

for dual auth in zapier, u can set up separate triggers/actions for each account type. manage the auth in ur app code to handle logic between em. it’s kinda hacky but it’s what works, just treat em as diff connections for same app.

4

Zapier doesn’t natively support this since each app instance handles one auth flow. But I’ve built something similar using connection parameters during auth. Add extra fields to your auth config so users can specify account identifiers or connection purposes. Then your triggers and actions can reference these stored parameters to figure out which account to hit for API calls. Just store enough metadata during auth so your app logic can tell the connections apart later. Users will still create separate Zap connections for each account, but your app handles the routing internally based on the auth metadata you grab.