OAuth
Industry-standard delegation protocol — lets a user authorise an app to access their data without sharing a password.
Definition
OAuth 2.0 separates authentication from authorization: instead of giving an app your password, you authorise it for a specific scope at the provider's consent screen, and the app receives a short-lived access token plus refresh token. OAuth underpins Google, Microsoft, GitHub, and most SaaS API integrations. PKCE is the recommended flow for public clients.
When to use
See also
- SSO — Single sign-on — log in once with your identity provider and access many apps without re-authenticating.
- bearer token — An API credential passed in the HTTP Authorization header — the holder is presumed authorised, no further proof.
Mentioned in
- Best free n8n workflow templates to copy in 2026
- How to connect Google Calendar to Zapier
- How to connect HubSpot to Zapier without code
- How to connect QuickBooks to Zapier for automated bookkeeping
- How to connect Salesforce to Zapier: full setup guide
- How to fix n8n OAuth callback URL returning 401
- How to sync HubSpot deals to a Notion database with Make.com
- Slack call_rejected webhook event: what it means and how to handle it in n8n