FormForce

FormForce Architecture

FormForce is designed as a Salesforce-first data intake layer. All forms, submissions, and workflows are built around Salesforce object models, not generic form schemas.

Login & Access

FormForce requires you to be logged in to manage Salesforce connections, build forms, and view form submissions. Authentication ensures that your Salesforce orgs and forms are securely associated with your account.

You must be logged in to connect a Salesforce org.
All forms and submissions are linked to your user account.
If you log out, all active sessions and local form data are cleared from the browser.
Salesforce access tokens are never stored on the client side and are handled securely on the server.

Salesforce Connection

To connect FormForce with your Salesforce org, you need to create a Connected App inside Salesforce and retrieve your Consumer Key and Consumer Secret. These values allow FormForce to authenticate using your Salesforce org.

In Salesforce, go to Setup → App Manager.
Click New Connected App or New External Client App.
Enter the app name (e.g., FormForce) and your email address.
Under API (Enable OAuth Settings), check “Enable OAuth Settings”.
Enter https://formforce.tech/api/oauth/callback for Callback URL field. This value must match the Redirect URI inside FormForce; otherwise Salesforce will reject the connection.
Select OAuth scopes like:Access and manage user data via APIs (api) and Perform requests at any time (refresh_token, offline_access).
Save the app and wait a few minutes for Salesforce to process it.
Under the Settings tab, click the Consumer Key and Secret button in the OAuth Settings section.
Enter the verification code sent to your email and click verify.
Copy the Consumer Key and Consumer Secret from the Connected App details page.
Go back to FormForce and paste these values in the “Connect to Salesforce” form.
Paste the Consumer Key into the Client ID field and the Consumer Secret into the Client Secret field. Enter any name into the Org Name field.
Click the Connection Link below and, if it appears, enter your username and password on the org login screen. If your org is already open in the browser, the login screen does not appear. Then, click “Allow” to establish the connection.
During the first connection, FormForce deploys a small Apex package to your Salesforce org. This is a one-time process. If you connect the same org again, Salesforce may return an “Apex deploy error” because the package already exists. In this case, the connection is still successful and no action is required.
Each Salesforce org requires its own Connected App for security reasons.

Once the connection is established, a success message is displayed, and the connected orgs are listed at the bottom.
You can disconnect using the Disconnect button and reconnect later.
Using the Delete button will completely remove the org connection.
If a Salesforce Org is permanently removed, existing forms remain active and linked to that org shows “Org Missing”. To reconnect the form, open it in Edit mode and select a new (or newly reconnected) org.
Salesforce allows only one active org session per browser. If you want to connect multiple Salesforce orgs, make sure you are logged into the target org in your browser before connecting, or use a different browser profile or an incognito window. Otherwise, the authorization may fail due to Salesforce’s cross-org OAuth restrictions.
In other words, if you see a message like "Missing code or state parameter" on the screen, it means you are trying to connect a separate org while another org is open in the browser, and the org you are trying to connect is not currently open in the browser.
Authentication is browser-specific. To view or manage previously connected Salesforce orgs on a different browser or device, you must log in again using the same account.

Form Building

In this section, you can design forms connected to your Salesforce org. Each form will send its data directly to the selected Salesforce object. Make sure you have already connected at least one Salesforce org before creating a form.

Go to the Forms page and click Create New Form.
Enter the Object API Name (for example: Account or Lead).
Provide a Form Title, this is the name displayed to users.
From the Org to Send dropdown, select the connected Salesforce org that will receive the form submissions.
Under Add Fields, choose the type of field you want to include (Text, Number, Checkbox, etc.).
Click + Add Field to add it to your form.
Hover over the info icon (ⓘ) to see how field types are mapped to Salesforce fields. For example:
- Single Checkbox → Salesforce Checkbox
- Radio Buttons → Salesforce Picklist
- Multi-Checkbox → Salesforce Multi-Select Picklist
When deciding field types:
- Use Radio Buttons for a small number of single-choice options.
- Use a Dropdown for larger lists of single-choice options.
- Use Multi-Checkboxes for a few multiple-choice options.
- Use a Multi-Select Dropdown when there are many multi-choice options.
Click the upload icon () to fetch the list of available fields from the selected Salesforce object, including picklist values.
At the bottom, you’ll see a live form preview that updates as you add or edit fields.
Once your form is ready, click Create Form to save it.

Forms View & Submissions

All of your created forms are listed under the Forms section. Each form clearly displays the Salesforce Org it is connected to and the target Salesforce Object (e.g., Lead, Contact, or any custom object).

Form Actions

Every form includes a set of management actions that allow you to review, update, share, and process submissions.

View – Opens the form for manual entry. The form owner can create a record directly. Submissions can be sent to Salesforce immediately or saved for later review.
Edit – Allows changes to form fields, labels, settings, and Salesforce mapping.
Delete – Moves the form to the recycle bin, preventing further submissions but keeping existing records safe.
Records – Displays all submissions related to that form, including:
- User-submitted entries from the public link
- Records manually created by the form owner
- Tables and analytics for deeper review
- Option to send pending records to Salesforce
Share – Generates a public URL that can be shared anywhere. Public submissions are not sent to Salesforce directly. Instead, they appear in the Records section, allowing the admin or owner to review and approve before pushing them into Salesforce.

Submission Flow

Whether submissions come from the form owner or public users, everything is first collected inside FormForce. From there, administrators maintain full control over which entries are approved and sent into their Salesforce Org. Sent records are automatically deleted after 30 days.

Support & Feedback

Have questions or suggestions? We are here to help. Send your message to:paginablanca@gmail.com

Loading…

You must be logged in to connect a Salesforce org.

All forms and submissions are linked to your user account.

If you log out, all active sessions and local form data are cleared from the browser.

Salesforce access tokens are never stored on the client side and are handled securely on the server.

Salesforce Connection

In Salesforce, go to Setup → App Manager.

Click New Connected App or New External Client App.

Enter the app name (e.g., FormForce) and your email address.

Under API (Enable OAuth Settings), check “Enable OAuth Settings”.

Enter https://formforce.tech/api/oauth/callback for Callback URL field. This value must match the Redirect URI inside FormForce; otherwise Salesforce will reject the connection.

Select OAuth scopes like:Access and manage user data via APIs (api) and Perform requests at any time (refresh_token, offline_access).

Save the app and wait a few minutes for Salesforce to process it.

Under the Settings tab, click the Consumer Key and Secret button in the OAuth Settings section.

Enter the verification code sent to your email and click verify.

Copy the Consumer Key and Consumer Secret from the Connected App details page.

Go back to FormForce and paste these values in the “Connect to Salesforce” form.

Paste the Consumer Key into the Client ID field and the Consumer Secret into the Client Secret field. Enter any name into the Org Name field.

Click the Connection Link below and, if it appears, enter your username and password on the org login screen. If your org is already open in the browser, the login screen does not appear. Then, click “Allow” to establish the connection.

During the first connection, FormForce deploys a small Apex package to your Salesforce org. This is a one-time process. If you connect the same org again, Salesforce may return an “Apex deploy error” because the package already exists. In this case, the connection is still successful and no action is required.

Each Salesforce org requires its own Connected App for security reasons.

Once the connection is established, a success message is displayed, and the connected orgs are listed at the bottom.

You can disconnect using the Disconnect button and reconnect later.

Using the Delete button will completely remove the org connection.

If a Salesforce Org is permanently removed, existing forms remain active and linked to that org shows “Org Missing”. To reconnect the form, open it in Edit mode and select a new (or newly reconnected) org.

Salesforce allows only one active org session per browser. If you want to connect multiple Salesforce orgs, make sure you are logged into the target org in your browser before connecting, or use a different browser profile or an incognito window. Otherwise, the authorization may fail due to Salesforce’s cross-org OAuth restrictions.

In other words, if you see a message like "Missing code or state parameter" on the screen, it means you are trying to connect a separate org while another org is open in the browser, and the org you are trying to connect is not currently open in the browser.

Authentication is browser-specific. To view or manage previously connected Salesforce orgs on a different browser or device, you must log in again using the same account.

Form Building

Go to the Forms page and click Create New Form.

Enter the Object API Name (for example: Account or Lead).

Provide a Form Title, this is the name displayed to users.

From the Org to Send dropdown, select the connected Salesforce org that will receive the form submissions.

Under Add Fields, choose the type of field you want to include (Text, Number, Checkbox, etc.).

Click + Add Field to add it to your form.

Hover over the info icon (ⓘ) to see how field types are mapped to Salesforce fields. For example:

Single Checkbox → Salesforce Checkbox
Radio Buttons → Salesforce Picklist
Multi-Checkbox → Salesforce Multi-Select Picklist

When deciding field types:

Use Radio Buttons for a small number of single-choice options.
Use a Dropdown for larger lists of single-choice options.
Use Multi-Checkboxes for a few multiple-choice options.
Use a Multi-Select Dropdown when there are many multi-choice options.

Click the upload icon () to fetch the list of available fields from the selected Salesforce object, including picklist values.

At the bottom, you’ll see a live form preview that updates as you add or edit fields.

Once your form is ready, click Create Form to save it.

Forms View & Submissions

Form Actions

Every form includes a set of management actions that allow you to review, update, share, and process submissions.

View – Opens the form for manual entry. The form owner can create a record directly. Submissions can be sent to Salesforce immediately or saved for later review.

Edit – Allows changes to form fields, labels, settings, and Salesforce mapping.

Delete – Moves the form to the recycle bin, preventing further submissions but keeping existing records safe.

Records – Displays all submissions related to that form, including:

User-submitted entries from the public link
Records manually created by the form owner
Tables and analytics for deeper review
Option to send pending records to Salesforce

Share – Generates a public URL that can be shared anywhere. Public submissions are not sent to Salesforce directly. Instead, they appear in the Records section, allowing the admin or owner to review and approve before pushing them into Salesforce.

Submission Flow