Also for Dynamics 365Consent records
When your org has the consent objects, a ticked box makes a ContactPointConsent for the data use purpose you choose, with its ContactPointEmail found or made under the contact’s Individual. In the same all-or-nothing request.
Salesforce
Forms that write straight into Salesforce.
Connect your org, drag its fields onto a form, and put it on your website with one line. Every answer becomes a record on the right object, linked to the right contact, the moment it is sent.
- Contacts, cases, leads and your own objects
- No duplicates: matched on your fields, or upserted by an external id
- One request per submission: all or nothing
How it works
Your org, your app, your rules.
Formscoop connects through an External Client App you create in your own org, so you decide what it may do and can switch it off at any moment.
- 1
Create an External Client App
Once, in Setup: switch on OAuth, paste the callback address the builder shows, and add the api and refresh_token scopes. Formscoop signs in with the OAuth web-server flow and PKCE.
- 2
Sign in to your org
Add the connection with the consumer key and secret, and sign in through login.salesforce.com, test.salesforce.com for a sandbox, or your own My Domain.
- 3
Drag fields onto the form
The builder lists the objects the signed-in user may create, with their fields. Drag them onto the form, publish, and paste one line on your website.
You need a Salesforce edition with API access, such as Enterprise, Unlimited, Performance or Developer Edition.
Several objects
A contact and the case it raised. In one request.
One form can create records on several objects and link them: the case to the contact, the files to the case.
Everything a submission writes goes to Salesforce in a single Composite request, all or nothing. If Salesforce refuses one record, none of them is written, and the submission shows why.
- Matching finds an existing record by the fields you choose, and updates the oldest match instead of creating a duplicate
- Links from a submission open the record in Lightning
- Records are written as the user who signed in, so permission sets and field-level security apply
- Matching on an External ID field becomes one upsert, so two people sending at the same moment never make two records
- One submission
-
One Composite requestContactfound by email and updated, or createdCasecreated, linked to the contactContentVersionthe uploaded files, as Salesforce Files on the case
All of it, or none of it
Field types
Salesforce fields, on a form.
Each Salesforce field type becomes the form field that suits it, with its values taken from your org.
| In Salesforce | On the form |
|---|---|
| Text, email, phone, number, date and checkbox | The matching form field |
| Picklist | A choice, with the value kept as text |
| Multi-select picklist | Several choices, joined with semicolons |
| Lookup to one object | A choice of existing records, from a list view or a filter |
| Record type | A choice of the object’s record types by name, or a fixed one |
| Dependent picklist | Only the options that go with the controlling answer: the form filters as people answer, and the server checks |
| Files | File uploads, saved as Salesforce Files on the record the form creates |
More than records
Consent, personal links and approval, built in.
The same tools as for Dynamics 365, made to fit Salesforce.
Personal links
A signed link opens the form filled in from one Salesforce record and updates that record. A flow, Zapier or the API asks for it with the record’s 15- or 18-character id.
Approval before publishing
On Business, contributors ask and an administrator publishes. On every plan, each published version is kept, with what changed, and can be put back.
Security
Your keys stay in Key Vault.
A public form is a door into your org. These are the locks on it.
Your own app
Formscoop signs in through an External Client App in your org, with the OAuth web-server flow and PKCE. Revoke the app in Salesforce and access ends.
Secrets in Key Vault
The consumer secret and the sign-in are kept in Azure Key Vault, never in the database, and never shown again.
A dedicated integration user
Records are written as the user who signed in. Use an integration user with Create and Read on the objects your forms need, and nothing more.
Your data, your choice
Decide per form what happens to the answers.
A newsletter sign-up and a complaint about an invoice do not deserve the same treatment. Each form says what it keeps, and the builder holds to it.
Keep nothing
Answers pass straight through to Dynamics 365 or Salesforce and are never stored by Formscoop. Only a count per day survives, so you can still see the form is working.
Keep a copy
A submissions overview with search, CSV export and a retry button for anything your CRM refused. Copies delete themselves after 7 to 365 days.
Email every submission
The answers, plus links to the records that were created, sent to whoever handles them. Reply and you are writing back to the person who asked.
Your brand
Every form looks like it was built by your web team.
Colours, font, corner rounding, field and button style, spacing and your logo, saved as a theme the whole company shares. Change the theme and every form wearing it follows, live ones included.
Forms render in their own isolated frame on your page, so your website's styles cannot break a form, and a form's styles cannot leak into your website.
Embedding
One line on your website.
Paste the snippet wherever the form should appear. It sizes itself to the page, on a phone as much as on a desktop.
<div data-pp-form="your-form-id"></div>
<script src="https://formscoop.com/embed/forms.js" async></script>- Works in WordPress, Webflow, Sitecore, SharePoint and single page apps
- An iframe for sites that strip scripts, and a hosted page for everything else
- Pass in campaign codes and other hidden values from the page
Your first Salesforce form could be live this afternoon.
Sign up, create a workspace, connect your org and start from a template.