Connect your WordPress forms.
Start inside WordPress. Add a configured mail provider, verification service or your own webhook receiver when the job calls for it.
A connection should have a clear purpose.
The plugin's native connections are listed below with their edition and setup requirements. Buying Pro does not supply a provider account or remove that service's verification, limits or charges.
- WordPressFree
Build and publish forms with a block, shortcode or guided placement. Accepted entries stay in the WordPress site.
What you need: An eligible WordPress and PHP version, plus a published form.
- WordPress mailFree
Use the site's normal mail route, including a host or another WordPress mail plugin that already configures it.
What you need: A valid sender and a working, tested site mail setup.
- SMTP serverPro
Send Accessible Forms mail through a dedicated SMTP connection. An optional safe-failure fallback can use WordPress mail.
What you need: Your server, port, encryption and authentication settings. Test both routes before enabling fallback.
- Resend APIPro
Send form mail through HTTPS and keep provider references. Configured callbacks can add recipient-level delivery evidence.
What you need: Your sending key, a verified sender and, for tracking, the callback and signing secret.
- Mailtrap Email SendingPro
Use the Email Sending API for notifications, receipts, replies and test emails. This is distinct from Email Sandbox.
What you need: Your Email Sending token and verified sender. The demo sender is limited to the Mailtrap account owner.
- Self-hosted ALTCHAFree
Add the optional self-hosted verification route alongside the core local spam controls.
What you need: Enable and test the chosen verification method, including the no-script and held-message paths.
- Cloudflare TurnstilePro
Use optional external verification for form spam protection. Missing or failed verification can hold a message for review.
What you need: Your Turnstile site key and secret, plus an appropriate site privacy disclosure.
- Signed submission webhooksPro
Send selected answers and event information to your own HTTPS endpoint. This supports a separately implemented downstream connection.
What you need: A public HTTPS receiver that verifies signatures, handles event identifiers and applies its own data policy.
Trace a notification in the right order.
The entry and its email are separate outcomes. These stages help you read the evidence without mistaking one for another.
Entry stored
The accepted form response is saved in WordPress before the notification is attempted.
Sending attempted
Background work sends through WordPress mail or the configured Pro transport.
Transport response
Acceptance, failure or uncertainty is recorded. Acceptance is a handoff, not an inbox guarantee.
Recipient evidence
Configured Pro API tracking can add delivery, delay or failure events for each recipient.
Build a custom connection deliberately.
There is no native Mailchimp, Slack, Google Sheets or Zapier connector bundled here. A Pro submission webhook can be the input to an integration you implement separately. The receiver owns signature checks, duplicate handling, downstream actions and deletion of its copy.
Submission webhooks pause outside a production environment and while test delivery is enabled. Use the plugin's controlled test event and validate your receiver before relying on the live path.
Know where the data goes.
The license connection does not send visitor form answers to this license service. Enabled mail routes receive message content; your configured webhook receives the selected submission information. The site owner must account for those services in its own privacy process.
Review privacy and retentionConfigure, send, then inspect.
Use the practical email guide to test a sender, configure tracking and interpret a recorded result.