Skip to content
Wrenform

Docs / Contact form guides

Send a Carrd form to your email with Wrenform

Point Carrd's Form element at your Wrenform endpoint, or embed an HTML form.

Last updated 2026-11-19View as Markdown
Type:         Custom
Send to URL:  https://wrenform.com/f/YOUR_FORM_ID
Method:       Default (or JSON)
Field names:  name, email, message

Create the form, copy the endpoint, and replace YOUR_FORM_ID. Just trying it out? A form without an account gives you an endpoint from one request, free for 250 submissions a month; you confirm it by email.

Carrd can send a form to any URL. Point it at Wrenform and each message is emailed to you, kept in your dashboard and spam-filtered. There are two ways.

With Carrd's Form element

Sending a form to a custom URL needs a paid Carrd Pro plan; Carrd's own form docs say which tier.

  1. Create a form in Wrenform and copy its endpoint from the Setup page.
  2. In Carrd, choose Add Element › Form, and set its Type to Custom.
  3. Choose Send to URL and paste your endpoint.
  4. Leave the method on Default (a standard form POST). JSON works too: Wrenform reads JSON bodies.
  5. Name the fields name, email and message. The email field becomes the reply-to of your notification.
  6. Don't add custom headers: the endpoint accepts only standard ones from a browser.
  7. Publish.

What the visitor sees after sending is set in Carrd's form settings.

With an Embed element

  1. Choose Add Element › Embed, and paste the HTML from the Embed element tab, with your form ID.
  2. Publish.

The form is unstyled at first; add a small <style> block in the same embed. This route keeps the _honey field. To send visitors to your own page after sending, set Redirect to in the form's settings in Wrenform. See redirects.

Allowed origins

In Wrenform, add your site under Allowed origins in the form's settings, with https://: your https://YOURSITE.carrd.co address and your custom domain if you have one.

Wrenform reads the page's address from the request's Origin header, or else its Referer. A request that carries neither is accepted only while Allowed origins is empty. So if the Form element route gets origin_not_allowed with your domain listed, leave the list empty for that form.

Spam and email

  • The hidden _honey field catches most bots. When it's filled, the submission goes to Spam and the sender still sees success. We haven't found a way to add it to Carrd's Form element; the Embed route has it.
  • No captcha is needed. The other checks run on both routes; see spam.
  • Want each message in another tool too? Add a webhook (Pro and Agency).
  • Submissions are stored in the EU. Free keeps them for 30 days, paid plans for 365 days.

Test it

Publish the site, open it in a private window and send the form. The submission should be in your dashboard and your inbox.

Common problems

  • 403 origin_not_allowed. The address you test from isn't in Allowed origins: often the carrd.co address while only the custom domain is listed. Add it, or see the section above. See errors.
  • Odd field names in the email. The email shows the names the form sends. Name each field name, email or message in the Form element's settings.
  • No Send to URL option. Your Carrd plan doesn't include custom URL forms. Use the Embed route.
  • Anything else. See troubleshooting.

Next steps

  • HTML guide: the full snippet, with the optional timing check.
  • Fields: more fields, checkboxes and JSON bodies.
  • Pricing: free for 250 submissions a month, paid plans from €5.

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