Website Builders
Connect a signup form built in Framer, Webflow, Elementor, or Carrd to Nashra by pointing it at an HTML form's action URL from Settings → Forms — which field names to use (email, name, WhatsApp phone), why not to name a field "website", and how to check that submissions reach Audience.
Before you start
Every builder below needs the same starting point: a Nashra form action URL. Nashra doesn't give you a snippet to embed — your builder draws the form, and Nashra receives what it submits.
Open Settings → Forms
Click New HTML form, or open an existing one. Pick a Response type — Redirect sends visitors to a thank-you page, JSON returns a response for code to handle — and add any Auto-tag submissions. Redirect needs a Thank-you URL. See HTML Forms & Form Actions for every option.
Copy the endpoint
Click Generate endpoint, then Copy link. The URL looks like https://app.nashra.ai/api/subscribe/… — that's the action URL you'll paste into each builder below.
If you're wiring up more than one builder, give each its own HTML form and auto-tag — framer-site, webflow-site, and so on — so you can tell signups apart later in Audience. The Forms list also shows how many subscribers each form has brought in.
Name your fields
Whichever builder you use, the inputs need names Nashra recognizes:
| Field | Name |
|---|---|
| Email (required) | email |
| First and last name | first_name, last_name |
| WhatsApp number (optional) | phone — in international format (+971…), or a local number plus a phone_country field with a two-letter country code |
| Custom fields | The field's data name — click View form fields in the form's dialog to copy them |
Don't name any input website. Nashra uses that name as a hidden spam trap: a submission that fills it gets a normal-looking success, but no subscriber is created. If your form asks for a site URL, call the field something else — or create a custom field named website, which switches the trap off for your workspace.
Framer
Framer's Form component can submit to a URL of your choice instead of Framer's own handler.
Add a Form component
Insert Framer's Form component onto your page from the Insert panel.
Find the submit destination
Select the form and open its properties panel. Look for the setting that sends submissions to a URL of your choice instead of Framer's built-in inbox — the exact label shifts between Framer versions, but it sits with the form's other submit options.
Paste your Nashra action URL
Set the method to POST if you're asked to choose one.
Name the email input
Open the email field's own settings and set its name to email — that's the key Framer submits it under.
If your version of Framer doesn't expose a custom submit URL on the Form component, drop in a Code or Embed component and write a plain HTML form instead — set its action attribute directly. See Form action URLs for a ready-to-paste example.
Webflow
Webflow forms can POST directly to an external URL instead of Webflow's own form handler.
Add a Form Block
Drag a Form Block onto your page from the Add panel.
Open the form's settings
Select the form and open its Settings panel — the gear icon in the right sidebar.
Switch to a custom action
Set the form's action to your Nashra action URL and switch its submit behavior to custom, instead of Webflow's own handler.
Name the email input
Select the email field and set its Name to email in the field's settings. That's the key Webflow submits it under.
Elementor
Elementor Pro's Form widget — the WordPress page-builder plugin, not Nashra's own WordPress plugin — posts to any URL through its Webhook action.
Add a Form widget
Drag Elementor's Form widget onto the page. This widget ships with Elementor Pro.
Set the email field's ID
Select the email field, open its Advanced tab, and set the Field ID to email.
Add a Webhook action
Under the form's Actions After Submit settings, add a Webhook action and paste in your Nashra action URL.
Update the page
Publish or update the page so the live form uses the new action.
Elementor calls the webhook from its own server, not as a browser form submit. Set the HTML form's Response type to JSON instead of Redirect — see Redirect vs. JSON response.
Carrd
Carrd's form element has a dedicated action field built for exactly this.
Add a Form element
Drag a Form element onto your Carrd site.
Add an email field
Use Carrd's built-in Email field type. If you build it as a plain text field instead, name it email.
Paste your action URL
In the form element's properties, find Carrd's form action field and paste your Nashra action URL.
Publish
Publish your site so the live form points at the new action.
Verifying a submission arrived
Submit a real test
Fill out the live form yourself, not a preview or draft mode — some builders don't fire real submissions until the site is published.
Open Audience
Go to Audience and filter by the auto-tag you set on this form, or search for the test email directly.
Confirm it landed
Check that the subscriber shows up with the right tags and any custom fields you configured.
If your form's double opt-in is on, the test subscriber shows as unconfirmed until you click the link in the confirmation email.
If nothing shows up, check these in order:
- The action URL — a typo in the pasted URL is the most common cause.
- The email field's name — it must be
email. Nashra also acceptsEmail,EMAIL,eMail,E-mail, andE-Mail, but it won't map a field namedcontact_emailorsignup_email— rename the field. - A field named
website— the spam trap above. The submission looks successful, but nothing is saved. - A required custom field — a custom field marked required in Audience → Fields must be in every HTML form, or the submission is rejected.
Visitors never see a CAPTCHA. Besides the spam trap, Nashra checks each signup's reputation: blatant spam gets a normal-looking success without being saved, and likely spam is saved with a mark that Audience's spam cleanup takes into account.
Form action URLs accept 10 submissions a minute from one visitor's IP address, and 10 attempts per 10 minutes for the same email address. That covers ordinary traffic with room to spare — if a launch on a busy shared network pushes past it, see Rate Limits.