My team is setting up an integration with Zapier, so that our clients (other companies) can authorize Zapier to send requests to our service on their behalf.
We were setting up OAuth v2 authentication for our integration, but ran into a problem. We noticed that Zapier goes through the OAuth flow for each new Zap. This is a problem for us because we really only need a company to authorize Zapier once. This also seems redundant to us, because scopes are defined in the Zapier Integration OAuth setup - so each token would have the same scopes.
Is there an option in Zapier to specify the behavior: in the case where user A has already authorized integration B, Zapier should re-use the existing token for new Zaps?
Or, can you shed light on what considerations we might be missing?
Best answer by ahoustonfloydView original