FORMHUSH / Carrd

Filter Carrd contact form spam

Send a Carrd Custom URL form to FormHush with the correct field IDs and encoding. Include the website honeypot and verify errors and redirects.

Carrd’s Custom URL form can send submissions to an external endpoint. Use it to connect a contact form to FormHush while keeping your page layout.

Configure a Custom URL form

Carrd lists Custom forms as a Pro Plus feature or higher. Confirm your plan supports it before editing. See Carrd’s Custom form documentation.

Choose a Custom URL form and use your provisioned FormHush endpoint. Select POST and URL-encoded data. Map the field IDs to name, email and message, then add an empty hidden website field that is included in the request. Do not use a real company website input for that key.

The following HTML shows the required request structure; it is also suitable for an HTML embed if your plan allows one.

Before connecting

The site is a preview. Accounts and forms are provisioned by an operator; the dashboard does not create them. Obtain a provisioned form ID and have the operator configure allowed origins, notification destinations and any thank-you URL before using the integration.

The examples use https://api.formhush.com/f/example-contact. Replace the illustrative example-contact ID with your provisioned ID; it is not a live demo form. Keep account keys out of public markup. Browser requests must come from an exact allowed origin, including the scheme and any port.

<form action="https://api.formhush.com/f/example-contact" method="POST">
  <label for="contact-name">Name</label>
  <input id="contact-name" name="name" maxlength="120" autocomplete="name">
  <label for="contact-email">Email</label>
  <input id="contact-email" name="email" type="email" maxlength="254" autocomplete="email">
  <label for="contact-message">Message</label>
  <textarea id="contact-message" name="message" maxlength="8000" required></textarea>
  <input name="website" type="text" hidden tabindex="-1" autocomplete="off">
  <button type="submit">Send message</button>
</form>

Check the serialized request

Confirm the submitted field keys in browser developer tools. Display labels do not necessarily determine the serialized keys. Missing website produces HTTP 400; a filled honeypot is accepted and stored as spam.

Use the native POST route if you want a server-side thank-you redirect. If your Carrd setup submits with AJAX, confirm how it displays the accepted response and errors instead of assuming a redirect will navigate the whole page.

Fields and thank-you behaviour

message is required, up to 8,000 characters. name is optional, up to 120 characters; email is optional, up to 254 characters and must be valid when supplied. The website string is mandatory and must stay empty for a legitimate visitor. A filled honeypot is stored as spam, not silently discarded.

Only JSON and URL-encoded POST bodies are accepted, with a 16,384-byte limit. Additional fields are not stored. FormHush does not use _gotcha, and a submitted _redirect does not control navigation.

For a native URL-encoded form, the operator sets the form’s HTTPS thank_you_url during provisioning. An accepted request then returns HTTP 303 to that URL. Without it, the endpoint returns HTTP 201 JSON. JSON requests always receive JSON; a JavaScript form handles its own success state or navigation after checking the response.

Classification, delivery and retention

Rules check the honeypot and known spam patterns first. When configured, Jev classifies the remaining message text after email addresses and phone numbers are masked. That masking is not complete anonymisation. Ambiguous decisions stay in Needs review without automatic forwarding.

Real leads and urgent messages are queued for configured destinations. When AI is unavailable, remaining accepted messages become Unsorted and are also queued; deterministic spam rules still apply. Delivery adapters support email, Slack, Telegram and webhooks, but need operator configuration. The email provider is not yet selected. Retries do not guarantee that a third party receives a message.

Submissions and related notification jobs are deleted after 30 days by scheduled cleanup. Copies sent to your channels follow those services’ retention policies. Processing can involve the United States; see the privacy policy for providers and details.

Test the complete flow

1. Test from an allowed origin using a provisioned form. Submit a clear enquiry and check its stored result in the dashboard.
2. Check delivery separately, using a configured test destination. An accepted response alone does not prove notification delivery.
3. Send a nonempty message with website filled to verify that it is stored as spam without notification. An empty message is a validation error, not a spam verdict.
4. Confirm a missing honeypot or empty message returns HTTP 400, an unsupported body format returns HTTP 415, and a disallowed browser origin returns HTTP 403.
5. Verify the thank-you page or inline success message and preserve entered text on errors. Rate and monthly limits return HTTP 429; respect Retry-After before retrying. Check for a stored record after a network failure to avoid duplicate submissions.