SentientMail Form Builder connects your WordPress site to SentientMail, so every newsletter signup and form submission lands in your email audience automatically, ready for journeys, campaigns, and transactional email.
Newsletter signups in two minutes
Everything else a small site needs from forms
{all_fields}, {field_id="2"}, …)The plugin works without a SentientMail account too. Forms, entries, and notifications are fully functional standalone. Connect an account when you’re ready to grow your list.
This plugin can connect to five named external services, and it can send
submissions to a webhook address you choose. All of it is optional: with none of
it configured, forms, entries and email notifications work entirely on your own
site and no data leaves it. The keyword blocklist is not one of them; it is
matched on your own server and sends nothing anywhere.
SentientMail is a hosted email marketing and transactional email platform, operated
by us. It is what the plugin syncs your form submissions into, so that signups
become contacts you can send campaigns and journeys to.
It is used only after you paste a SentientMail Events API key on the Get Started
screen. Nothing is sent before that.
What is sent, and when:
Requests go to https://app.sentientmail.com over HTTPS and are authenticated with
the key you supplied. Forms without audience sync enabled send nothing.
Terms of service: https://sentientmail.com/terms.html
Privacy policy: https://sentientmail.com/privacy.html
Mailchimp is a hosted email marketing platform operated by Intuit. It is used
only if you enter your own Mailchimp API key under Settings AND switch Mailchimp
on for a particular form, where you also choose which audience to add people to.
It is off by default. With no key entered, no form makes any request to
Mailchimp.
Your Mailchimp API key ends in a dash and a short datacenter code, such as
-us21. The plugin reads that code out of the key to work out which Mailchimp
server your account is on, so there is no server address for you to enter. A key
without that suffix is refused, and nothing is sent.
What is sent, and when:
If the form contains a consent checkbox, nothing is sent to Mailchimp at all
unless the visitor ticked it.
New subscribers are added as “pending” by default, which is Mailchimp’s double
opt-in: Mailchimp emails a confirmation link and nobody joins the audience until
they click it. You can choose single opt-in per form instead, which adds the
address immediately.
Requests go from your server to https://.api.mailchimp.com over
HTTPS, authenticated with the API key you supplied. The key is sent in an
Authorization header, is never written into a URL, is never shown again after you
save it, and is removed from any error message the plugin records.
Terms of service: https://mailchimp.com/legal/terms/
Privacy policy: https://mailchimp.com/legal/privacy/
Slack is a team messaging service operated by Salesforce. It is used only if you
create an incoming webhook in your own Slack workspace, paste its URL into a
form’s Integrations tab and switch Slack on for that form. It is off by default.
With no webhook URL saved, no form makes any request to Slack.
The URL must be an https://hooks.slack.com/ address; anything else is refused
rather than saved, so the field cannot be pointed at some other server.
What is sent, and when:
Requests go from your server to https://hooks.slack.com over HTTPS. The webhook
URL is the credential: it is never displayed again after you save it, and it is
removed from any error message the plugin records.
Terms of service: https://slack.com/terms-of-service
Privacy policy: https://slack.com/trust/privacy/privacy-policy
Turnstile is Cloudflare’s privacy-preserving CAPTCHA alternative. It is used only
if you enable it and enter your own Turnstile site key and secret key under
Settings. It is off by default.
What is sent, and when:
Terms of service: https://www.cloudflare.com/website-terms/
Privacy policy: https://www.cloudflare.com/privacypolicy/
Akismet is a spam-filtering service operated by Automattic. It is used only if
the Akismet plugin is installed and already set up with its own API key, AND you
tick “Akismet” in a form’s anti-spam settings. It is off by default. This plugin
never asks you for an Akismet key of its own and never stores one: it uses the
key Akismet already holds. With no key present, no request is made.
What is sent, and when:
Requests go from your server to https://rest.akismet.com over HTTPS, addressed
with your Akismet API key, which is how Akismet identifies the account making
the check. Nothing is sent from the visitor’s browser, and no Akismet script is
loaded on your pages.
If Akismet cannot be reached, or answers with anything other than a verdict, the
submission is accepted. A submission Akismet does call spam is kept as a spam
entry you can review and restore, not deleted.
Terms of service: https://akismet.com/tos/
Privacy policy: https://akismet.com/privacy/
Not a third-party service, but it does send data off your site, so it is
documented here with the rest.
A form can be given a webhook address under its Integrations tab. There is no
default and no address is built in: it goes wherever you type. When somebody
submits that form, this plugin sends that address a JSON request containing your
site address, the form’s ID and title, the entry ID, the time of submission, the
page the form was on, and the values the visitor entered. If you set a signing
secret, the request is also signed so the receiver can verify it came from you.
Requests go over HTTPS only, and cannot be aimed at addresses inside your own
server’s network. Whoever operates the address you enter decides what happens to
the data once it arrives, under their own terms and privacy policy. Remove the
address to stop the sending.