Skip to content
Wrenform

Docs / Switching

Switch from Web3Forms

Change the action URL and delete the access key. Then rename the few Web3Forms fields that Wrenform spells differently.

Last updated 2026-11-16View as Markdown
<!-- Before -->
<form action="https://api.web3forms.com/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <input type="hidden" name="subject" value="New message from my site">
  <input type="hidden" name="redirect" value="https://example.com/thanks">
  <input type="email" name="email" required>
  <textarea name="message" required></textarea>
  <input type="checkbox" name="botcheck" style="display: none;">
  <button type="submit">Send</button>
</form>

<!-- After -->
<form action="https://wrenform.com/f/YOUR_FORM_ID" method="POST">
  <input type="hidden" name="_subject" value="New message from my site">
  <input type="hidden" name="_redirect" value="https://example.com/thanks">
  <input type="email" name="email" required>
  <textarea name="message" required></textarea>
  <input type="text" name="_honey" style="display:none" tabindex="-1" autocomplete="off">
  <button type="submit">Send</button>
</form>

Steps

  1. Create a form in Wrenform and copy its form ID.
  2. Replace the form's action with https://wrenform.com/f/YOUR_FORM_ID. Keep method="POST".
  3. Delete the hidden access_key field. Your form ID is in the URL instead, so there is no key in the page.
  4. Rename the fields in the table below.
  5. Recreate your settings: recipients, allowed origins, and the thank-you page (Redirect to).
  6. Deploy and send a test.

Field mapping

Web3Forms field names checked against Web3Forms' own docs on 2026-11-16.

In your Web3Forms form In Wrenform
access_key (or the older apikey) Delete it. The form ID is in the action URL
botcheck checkbox honeypot Replace it with the hidden text field _honey, as in the snippet above. See spam
redirect Rename to _redirect, or set Redirect to in the settings. Its origin must be in Allowed origins. See redirects
subject (hidden, a fixed subject) Rename to _subject
subject (a text field visitors fill in) Keep it; it's stored as a normal field. Set Email subject to {field:subject} in the form's settings
replyto Rename to _replyto
email field Works as is. It becomes the reply-to
from_name Delete it. The email names your form; otherwise it would arrive as a normal field
ccemail Delete it. Add each address under Recipients instead
webhook Delete it. Add the URL under Webhooks in the form's settings
attachment and other file inputs Not supported yet. Text fields still arrive; files are dropped
hCaptcha or reCAPTCHA (h-captcha-response, recaptcha_response) Not needed. Remove the widget and its script; spam filtering is on by default. Cloudflare Turnstile with your own keys is optional; see spam

Fields we read are listed in fields. Any other field is stored as data.

What's different

  • Recipients confirm their address. Each address you add gets a confirmation email and receives submissions only after it confirms. Your sign-in address is confirmed from the start. See notifications.
  • Spam rules run on every form, with no CAPTCHA. A honeypot, a timing check, rate limits and a content score, on every plan. Spam goes to the form's Spam tab, sends no email and doesn't count toward your quota. See spam.
  • Webhooks are set in the dashboard, not in the page. They are signed, retried, and on the Pro and Agency plans. See webhooks.

JavaScript and AJAX forms

If your code posts with fetch and an Accept: application/json header, keep it, but update how it reads the answer. Web3Forms answers with success and message; we answer with:

  • Success: 200 with { "ok": true, "id": "…" }.
  • Error: a 4xx or 5xx with { "ok": false, "error": { "code", "message", "docs" } }.

Read ok and error.message. Our error codes list every case. Using @web3forms/react? Replace it with a plain fetch, as in the React guide.

Your old submissions

Copy anything you need from Web3Forms before you close your account there. We don't import past submissions yet.

Test it

Send the form from your live site. You should land on your thank-you page (or ours), see the submission in your Wrenform dashboard, and get an email. Then fill the hidden _honey field with your browser's developer tools and send again: it should land in the Spam tab.

Common problems

  • Redirect goes to our page, not yours. The field is still named redirect, or its origin isn't in Allowed origins.
  • A field called access_key or botcheck shows up in the dashboard. It's still in the form. Delete it.
  • No email arrives. The recipient hasn't confirmed yet. Check spam, then resend it from the form's settings.
  • origin_not_allowed. Add your site to Allowed origins, or leave the list empty while you test.

Next steps

Something wrong or unclear on this page? Report a problem: write to hello [at] wrenform.com with the page address (/docs/migrate/web3forms).