Better Oauth2.0 workflow for Pipedrive CRM with Supabase

This workflow provides an OAuth 2.0 auth token refresh process for better control. Developers can utilize it as an alternative to n8n's built-in OAuth flow to achieve improved control and visibility. In this template, I've used [Pipedrive API](https://developers.pipedrive.com/docs/api/v1/Oauthget-tokens), but users can apply it with any app that requires the authorizationcode for token access.

This resolves the issue of manually refreshing the OAuth 2.0 token when it expires, or when n8n's native OAuth stops working.

What you need to replicate this

1. Your database with a pre-existing table for storing authentication tokens and associated information. I'm using Supabase in this example, but you can also employ a self-hosted MySQL.

Here's a [quick video](https://go.screenpal.com/watch/cZiXhEV8N0y) on setting up the Supabase table.

2. Create a client app for your chosen application that you want to access via the API.

3. After duplicating the template:

a. Add credentials to your database and connect the DB nodes in all 3 workflows.