Keep nothing
Answers pass straight through to Dynamics 365 and are never stored by the form builder. Only a count per day survives, so you can still see the form is working.
Dynamics 365 · Dataverse
Forms that land straight in Dynamics 365.
Drag your Dynamics 365 columns onto a form, brand it, and put it on your website with one line. Every answer arrives in the right table, linked to the right record, the moment it is sent.
- Contacts, cases, leads and your own tables
- No duplicates: recognise people by email
- Store nothing, or keep a copy. Your choice per form
How it works
Three steps, and none of them is code.
Built for the people who own the website and the customer process, not for the people who would otherwise have to write an integration for them.
- 1
Connect your environment
Add your Dynamics 365 environment with an application user. Or start in the built-in demonstration environment and connect yours when it is ready.
- 2
Drag, drop and map
Drag columns straight from your tables, or add a field and choose where its answer goes. Choices, lengths and required fields come from Dynamics 365 itself. Split a long form into steps, and show a question only when an earlier answer calls for it.
- 3
Publish and embed
Publish, copy one line onto your website, done. Edits stay in draft until you publish again, so the live form never changes under a visitor.
Several tables
A contact and the case it raised. In one go.
One form can write to as many tables as the process needs. Add the Contact and the Case, and the builder links the case to the contact through the right lookup without being asked.
Everything a submission writes is sent as one transaction. Either the contact and the case both arrive, or neither does: never a customer on record with a question nobody can see.
- Find the existing contact by email instead of creating a duplicate
- Fixed values on every row: origin Web, the right queue, the lead source
- Answers without a column are kept as a readable summary on the record
- A test run in the builder shows exactly which rows a submission would write
Contact us
1
Contact
found by email, or created
2
Case
created, linked to the contact
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 a copy
A submissions overview with search, CSV export and a retry button for anything Dynamics 365 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://forms.powerpete.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
Try it
This is a real form.
It is embedded on this page with the same snippet you would use, and it is connected to the demonstration environment: it validates, plans and records your submission exactly like a live one, and writes nothing anywhere.
Use sanne.devries@example.com as the email address to watch it recognise an existing contact instead of creating a new one.
Security
Built to sit in front of your CRM.
A public form is a door into Dynamics 365. These are the locks on it.
Least privilege
Forms write as an application user you create, with a security role that can create the rows your forms need and nothing else.
Secrets in Key Vault
Client secrets and sign-ins are kept in Azure Key Vault and never written to the database, a log or a screen.
Checked on the server
Every answer is validated against the published form on the server, whatever the browser claims. A choice the form never offered is refused.
Bots stay out
A hidden honeypot, a signed timing check and a limit per visitor. No captcha, so real customers are never slowed down.
Nothing leaks to the page
The public form never reveals which tables it writes to, its fixed values or who receives the email.
Your websites only
Limit each form to your own domains, so nobody can put your form on somebody else's website.
Your next form could be live this afternoon.
Sign in with your Microsoft account, create a workspace, and start from the Contact us template.