Complete guide to configuring OAuth integrations for Google, Stripe, and Telegram in OpnForm
OpnForm supports several OAuth integrations that enable users to connect external services for enhanced functionality. This guide covers setting up Google, Stripe, and Telegram OAuth integrations.
OpnForm handles OAuth redirect URLs automatically. You don’t need to manually configure redirect URLs in your OAuth applications - the system generates them dynamically based on your domain configuration.
If you’re looking to add a new OAuth integration to OpnForm, check out the complete developer guide with architecture overview and implementation steps.
Authentication, Google One Tap, and Google Sheets integration for form data export
Payment processing integration for collecting payments through forms
Notification integration for form submission alerts via Telegram
Google OAuth enables user authentication and integrates with Google Sheets for exporting form submissions.
Create Google Cloud Project
Navigate to the Google Cloud Console and create a new project or select an existing one.
Enable APIs
Enable the following APIs for your project:
Configure OAuth Consent Screen
Create OAuth Credentials
For Google One Tap to work, ensure your domain is added to the authorized origins. This enables the seamless authentication widget to function properly.
Save the Client ID and Client Secret for environment configuration.
Configure Environment Variables
Add the following variables to your backend .env
file:
The Google Fonts API key is optional and only needed if you want to use Google Fonts in your forms.
Stripe OAuth enables payment processing capabilities within OpnForm, allowing you to collect payments through your forms.
Create Stripe Application
Configure Platform Settings
Get OAuth Credentials
Save the Client ID and Client Secret for environment configuration.
Configure Environment Variables
Add the following variables to your backend .env
file:
These OAuth credentials are separate from your regular Stripe API keys. The OAuth credentials enable connecting multiple Stripe accounts, while regular API keys are for direct payment processing.
Telegram OAuth enables notification integration, allowing OpnForm to send form submission alerts to Telegram chats.
Domain Requirement: Telegram requires that your bot is linked to a valid domain with HTTPS. Localhost URLs are not supported. For development, consider using a tunneling service like localtunnel to expose your local development server with a public HTTPS URL.
Create Telegram Bot
/newbot
Your bot token will look like: 123456789:ABCdefGHIjklMNOpqrsTUVwxyz
Link Domain to Bot
/setdomain
to @BotFatheryourdomain.com
or for development: abc123.loca.lt
)For Development: If you’re developing locally, use localtunnel to get a public HTTPS URL:
Use the provided .loca.lt
URL as your domain with BotFather.
Configure Environment Variables
Add the following variable to your backend .env
file:
The bot ID is automatically extracted from the bot token (the numeric part before the colon), so you don’t need to configure it separately.
Test Your Bot
You should receive a formatted message with form submission details.
Important Security Notes:
Google OAuth Issues
Common problems and solutions:
Stripe OAuth Issues
Common problems and solutions:
Telegram OAuth Issues
Common problems and solutions:
Verify Configuration
Check that all environment variables are set correctly and restart your application.
Test Authentication
Try logging in with each OAuth provider to ensure the authentication flow works.
Test Integrations
Monitor Logs
Check your application logs for any OAuth-related errors or warnings.
With properly configured OAuth integrations, your OpnForm installation will support seamless user authentication and powerful third-party service integrations.