Automation and integration
OAuth
OAuth is an open standard that lets a user give one application limited access to their account in another, such as letting an automation read a Google Calendar, without sharing their password.
How it works in practice
When you click "Connect to Google" or "Sign in with Microsoft" in an app and approve a list of permissions, that is OAuth 2.0. The app receives a token covering only those permissions, called scopes, and you can revoke it at any time without changing your password.
In automation work, OAuth decides whose account a workflow acts as and what it can touch. We connect integrations through service or admin accounts the client owns, ask for the narrowest scopes that do the job, and record which connection belongs to which workflow, so access can be removed cleanly when someone leaves.
A worked example
A finance team’s reporting workflow needs read access to Xero. It is connected through OAuth with read-only accounting scopes under a finance service account, so it cannot create or change transactions and does not break when a staff member leaves.
Examples in this glossary describe typical builds for companies of 1 to 1,000 people. They are not named client results.















