Form Settings

Form Settings

Submission Settings

• Thank You Message — The message shown to the respondent after a successful submission (up to 5,000 characters). Displayed on the confirmation page.
• Redirect URL (optional) — Instead of showing the thank-you message, redirect the respondent to an external URL after submission. Only HTTP and HTTPS URLs are accepted.

Spam Protection

Protect your forms from spam with multiple layers:

• Honeypot — A hidden field that bots fill in but humans do not see. If the hidden field contains a value, the submission is rejected. No configuration needed — just toggle it on.
• Google reCAPTCHA v3 — Invisible verification that scores each submission. Requires your reCAPTCHA site key and secret key (configured in your account’s integration settings).
• Cloudflare Turnstile — A privacy-friendly CAPTCHA alternative. Requires your Turnstile site key and secret.
• hCaptcha — Another CAPTCHA provider option. Requires your hCaptcha site key and secret.

You can enable multiple protections. If more than one CAPTCHA provider is enabled, they are checked in priority order: reCAPTCHA first, then Turnstile, then hCaptcha.

Email Notifications

Set up email notifications that are sent when the form is submitted. Each notification rule has:

• Name — A label for your reference.
• Enabled — Toggle the notification on or off.
• Recipients — Who receives the email:
  • Admin — The form owner and subaccount owner.
  • Submitter — The email address from the submission (auto-detected from the first email field).
  • Custom — One or more email addresses, comma-separated. Supports tokens like {{field.email}}.
• Subject — The email subject line. Supports tokens.
• Message — The email body. Supports tokens.
• Reply-To (optional) — Set a reply-to address. Supports tokens.
• Conditions (optional) — Only send the notification when conditions are met (same operators as conditional logic). Combine conditions with All or Any matching.

Available tokens for notifications:

• {{form.name}}, {{form.slug}}
• {{submission.id}}, {{submission.date}}, {{submission.time}}, {{submission.datetime}}
• {{date.today}}, {{date.now}}
• {{field.FIELD_KEY}} or {{FIELD_KEY}} — The value of any form field.

Webhooks

Send form submission data to external services in real time. Each webhook rule has:

• URL — The endpoint to send data to.
• Method — HTTP method: POST, GET, PUT, PATCH, or DELETE.
• Headers — Custom HTTP headers (e.g., for authentication).
• Payload Format — JSON or form-encoded.
• Include Submission Data — Whether to include the full field values in the payload.
• Custom Payload (optional) — A custom JSON template with token replacement.
• Conditions (optional) — Only fire the webhook when conditions are met.

Record Creation Rules

Automatically create contacts or custom entity records from form submissions. Each rule defines:

• Type — Whether to create a Contact or a Custom Entity Record.
• Entity Type — For entity records, which entity type to create (e.g., Project, Product).
• Field Mappings — Map each form field to a target field:
  • For contacts: first_name, last_name, email, phone, or custom:field_key for custom fields.
  • For entity records: any custom field key on the entity type.
  • For relationships: link to another record created by a different rule in the same form.

You can define multiple rules on a single form (e.g., create a Contact and a Project record, then link them via a relationship). Rules are processed in dependency order — parent records are created first so child records can reference them.