TopolearnA Zap can only read or change data in an app after you have given Zapier safe, limited permission to that account.
Before Zapier can read your Gmail or post in your Slack, you must give it permission. You do this once per account by creating an app connection (a saved, secure link between Zapier and one of your accounts).
When you add an app to a Zap, Zapier asks you to sign in to that app. Two common ways this works:
- OAuth: a pop-up from the app itself (for example Google) asks "Allow Zapier to access your account?". You never give Zapier your password; the app hands Zapier a permission slip instead.
- API key: some apps instead give you a long secret code in their settings. An API key is like a password for programs, so you paste it into Zapier and keep it private.
Zapier stores these credentials (the login details) encrypted, and a connection only allows what that account is permitted to do. If your account cannot delete records in the CRM, neither can your Zap.
One connection can be reused in many Zaps. Give connections clear names such as "Gmail - Support inbox" so you pick the right one later, and remove ones you no longer use.
Connections sometimes expire or break: you changed your password, your company added new security rules, or the account lost permissions. Zaps that use a broken connection start failing until you reconnect it from the app connections page.
On team accounts you can share a connection with colleagues so they can build Zaps with it without knowing the password, and administrators can control which apps people are allowed to connect.
Remember
- An app connection is Zapier's saved, encrypted permission to use one of your accounts
- OAuth means signing in through the app; an API key is a secret code you paste in
- Name connections clearly and reconnect them when they expire
Watch out for
- Building an important team Zap on a personal account connection that breaks when that person leaves.