Hello Make Community!
We’re exploring the development of a #Bubble.io application aimed at automating social media integrations through Make and the Make API. Our goal is to facilitate oauth authentication directly, without requiring users to manually input their ‘client ID’ and ‘client secret’ (required for the Make connections API). Instead, we aim to handle this process through OAuth flows, where users authorize our application to act on their behalf on various social media platforms. This would involve securely obtaining and managing OAuth tokens, bypassing the need for users to provide sensitive credentials. We’re interested in understanding the technical feasibility of implementing such an OAuth-centric approach within the Make ecosystem, leveraging Bubble.io for the user interface. How can we best architect this solution to ensure a secure and user-friendly experience?
Any advice, insights, or guidance from the community would be greatly appreciated!
Christophe