Register an OAuth application
Let your own app sign users in with their Formbot account.
Open this guide in the help center →
When to use this. Your product needs users to sign in with Formbot rather than creating another password.
What you’ll need. A Formbot sign-in and the exact callback URL of your application.
Find the right screen
Go to Settings → Manage Clients. This is where OAuth applications live, even though it sits under personal settings rather than under Account Management.
Add a client
Choose Add Client. Give it a name your users will recognize on the consent screen — they see this name when deciding whether to grant access.
Set the redirect URI
Enter the exact URL Formbot should return the user to after they approve. It must match your application's callback exactly, including the scheme and any trailing path; a mismatch is the most common cause of a failed authorization.
Store the credential
Formbot shows the client credential once, with a warning to keep it safe. Put it in your server's secret store immediately — never in frontend code, a public repository, or a screenshot.
Test the round trip
Send a user through the authorization flow. They should see your application name on the consent screen and land back on your redirect URI with a code to exchange.
Rotate if exposed
If the credential leaks, edit the client and issue a new one, then update your server. Treat a leaked client secret as urgently as a leaked password.
How to know it worked
A user can authorize your app and land back on your redirect URI with a code.
Features covered
- OAuth applications
- Redirect URI
- Client credentials