A lot of the APIs I want to connect to use OAuth 2.0, and I want to make sure I’m handling authentication the right way rather than doing something hacky. Does Tines have native support for OAuth flows, and how does token refresh work? Would love a clear explanation of how this is typically set up.
Tines has native support for OAuth 2.0 through its credential system. For the client credentials flow (common in server-to-server integrations like CrowdStrike or Microsoft), you configure the credential with your client ID, client secret, and token URL, and Tines automatically handles requesting and refreshing tokens as needed. You don’t have to manage token expiry yourself.
For authorization code flow, which involves user-facing consent, the setup is a bit more involved but Tines supports this too. The credential stores the necessary tokens and handles refresh using the refresh token when the access token expires.
Once your OAuth credential is configured, you reference it in your HTTP actions and Tines injects the current valid token into the request header automatically. Detailed Tines Credentials docs can be found here!