Formstack is an online form builder and data collection platform. Integrating Formstack with Frontegg lets your application manage forms and fields, read and create submissions, organize folders, and manage webhooks on behalf of your users — all through Frontegg's integration layer. You can authenticate with either OAuth 2.0 (recommended when connecting on behalf of multiple users) or a Personal Access Token. Formstack's OAuth has no scope model — a token grants full account access.
Prerequisites
Prerequisites
- A Formstack account
- For OAuth: access to the API section of your account to register an app
- For a Personal Access Token: an admin with the token-generation ability enabled
You register an OAuth 2.0 application in Formstack. The app provides the Client ID and Client Secret and defines the redirect URI that Formstack returns users to after they authorize access.
Sign in to Formstack and open the API section of your account settings. Click New Application.
Enter the application details:
- Name — A descriptive name, for example
Frontegg Integration. - Redirect URI — Your Frontegg Redirect URL:
https://YOUR_MCP_GATEWAY_URL/integration-callback
Save the application.
Open the application. Formstack displays the Client ID and Client Secret. Copy both values.
Keep your Client Secret safe
Keep your Client Secret safe
Treat the Client Secret like a password. Never expose it in client-side code or commit it to version control.
If you are connecting a single account rather than authorizing multiple users, you can use a Personal Access Token (PAT) instead of an OAuth app:
- In Formstack, open your account settings and go to Personal Access Tokens.
- Generate a new token and copy it. Formstack PATs are prefixed with
fs_pat_.
Personal Access Token generation must be enabled by an Organization Admin before it is available.
Configure the integration in the Frontegg portal using the method you chose:
- Open the Frontegg portal and navigate to [ENVIRONMENT] → Integrations → Formstack.
- For OAuth, enter the Client ID and Client Secret. For a Personal Access Token, enter the token in the Access Token field instead.
- Click Save.
Keep your credentials secure
Keep your credentials secure
Never share or commit your Client Secret or Personal Access Token to version control.